Fix timestamp() setting a key named "null" in some cases #1820
The previous PR introduced a bug where a model could end up with a key named "null" if the user specified a custom
This checks if a
If we give only created_at attribute in the array it is taking undefined in the insert query instead of updated_at.
For above model declaration the query is going like
If we give like
Then the query is going like
So, I have given false value for the > hasTimestamps then it is working.
I am referring the published version email@example.com only.…
On Thu, Jun 14, 2018 at 4:38 PM, Ricardo Graça ***@***.***> wrote: Have you tried the code that is in this change or are you referring only to the published version 0.13.3? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1820 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlchsrdzscGFrlb-xiHeclrQQbuuKeiAks5t8kQzgaJpZM4Tfmw6> .
-- Thanks & Regards,Meda AmaranadhSr.Software Development Engineer ------------------------------ westagilelabs.com LinkedIn <https://www.linkedin.com/in/thisisamar/>