Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update datetime_field.py #92

Merged
merged 1 commit into from Jun 8, 2015
Merged

Update datetime_field.py #92

merged 1 commit into from Jun 8, 2015

Conversation

veeloox
Copy link
Contributor

@veeloox veeloox commented Jun 8, 2015

auto_now_on_update return stored date instead of datetime.now()

auto_now_on_update return stored date instead of datetime.now()
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.7% when pulling 0ab9a82 on veeloox:veeloox-datetime_field-patch into 7ec9114 on heynemann:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.7% when pulling 0ab9a82 on veeloox:veeloox-datetime_field-patch into 7ec9114 on heynemann:master.

heynemann added a commit that referenced this pull request Jun 8, 2015
@heynemann heynemann merged commit f07f1b2 into heynemann:master Jun 8, 2015
@Rey8d01
Copy link

Rey8d01 commented Oct 15, 2015

Really? Every time calling to_son() receive a new time? Even if you do not save (update) the document? That's not true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants