Re: why created_at is greater than updated_at while inserting data in table

and with this method created_at and updated_at both arguments will trigger the field update event with timezon.now(), is there any other method to enter only created_at at time of inserting On Wednesday, 28 November 2018 12:43:03 UTC+5:30, Ankit Khandewal wrote: > > hello, i am using thi

Re: why created_at is greater than updated_at while inserting data in table

is there any fix to this? On Wednesday, 28 November 2018 12:43:03 UTC+5:30, Ankit Khandewal wrote: > > hello, i am using this code to update created_at and updated_at in models: > created_at = models.DateTimeField(auto_now_add=True) > updated_at= models.DateTimeField(auto_n

why created_at is greater than updated_at while inserting data in table

hello, i am using this code to update created_at and updated_at in models: created_at = models.DateTimeField(auto_now_add=True) updated_at= models.DateTimeField(auto_now=True,null=True) but however there is created _at is greater than updated_at when data is inserted: created_at

get_or_delete leading to duplicate creation

Hello, I am using get_or_create method in my project and this is leading to creating duplicate for objects, there created_at time difference is in milliseconds, please report this issue to fix. -- You received this message because you are subscribed to the Google Groups "Django users" group.