#2688: failed save() with postgresql sometimes doesn't throw error until next
statement (which is 'set time zone')
-------------------------------------+-------------------------------------
Reporter: mail@… | Owner: zefciu
Type: Bug | Status: closed
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: psycopg | Triage Stage: Accepted
transactions timezone postgresql | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by zefciu):
* status: assigned => closed
* has_patch: 1 => 0
* resolution: => worksforme
Comment:
I have tried to reproduce this bug by putting the value of time.time() to
!DateField. My results:
* In current version of django it simply doesn't pass the validation.
* After disabling validation (by substituting all the `.to_python()` logic
with `return value` the !DatabaseError is returned immediately.
What's more. 5 years ago, when this bug was submitted psycopg was about
2.0.5. It's most likely that this effect was due to some bug in psycopg2,
as it didn't happen with other backends. As nobody provided a reproducible
case for this bug or submitted similar bugs from that time, we can assume
that this bug was fixed.
I suggest to close this bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/2688#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
