[patch] broken Timestamp on manual created Users using postgres/sqlite

[Ronny Pfannschmidt]

while adding a entry for unregistred Users i noticed, that the Model wont use correct timestamps for:

User.objects.get_or_create(username="UnReg",defaults={'id':-1})

,since its using LazyDate as default, wich does only the Date,
unfortunately Mysql is the only supported dbms accepted this, so i added a auto_now_add=True, wich resulted in sqlite and postgresql working, too

[[Cha0S]]

test

[Adrian Holovaty]

Could we get a unit test that verifies this? Also, what exactly does "broken timestamp" mean? Finally, I'm not in favor of the patch, because auto_now_add is a hack that I'd like to get rid of eventually. If nothing else, it should use default=datetime.datetime.now, taking advantage of the callable default functionality.

[Ronny Pfannschmidt <ronny.pfannschmidt@…>]

some dbms didnt accept the date from lazydate - but default=datetime.now is a better solution

[Ben Slavin]

Looks to me like this was solved in [4985], when LazyDate was pulled.

Please reopen if this didn't fix it for you, but it sounds like you were happy with the solution used to replace LazyDate.