Opened 20 hours ago
Last modified 54 minutes ago
#36078 closed Bug
Postgres date and time range fields change after saving object — at Initial Version
| Reported by: | Mapiarz | Owned by: | |
|---|---|---|---|
| Component: | contrib.postgres | Version: | 4.2 |
| Severity: | Normal | Keywords: | postgres |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This short test exemplifies the problem:
now = timezone.now() empty_range = psycopg2_range.DateTimeTZRange(empty=True) test_model = TestModel(range=psycopg2_range.DateTimeTZRange(now, now)) self.assertFalse(test_model.range.isempty) self.assertNotEqual(test_model.range, empty_range) test_model.save() test_model.refresh_from_db() self.assertTrue(test_model.range.isempty) self.assertEqual(test_model.range, empty_range)
I would expect the field value not to change after saving, and it should continue to have the lower, upper and boundary fields set.
Repro project: https://github.com/Mapiarz/django_postgres_range_repro/tree/master
Note:
See TracTickets
for help on using tickets.