Opened 17 years ago
Closed 17 years ago
#3748 closed (fixed)
[boulder-oracle] DateTimeField shows as "True" in admin
| Reported by: | Matt Boersma | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | other branch |
| Severity: | Keywords: | oracle | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Providing a default of "datetime.datetime.now()" or similar to a DateTimeField in a model leads to both form entry fields in the admin showing the value "True" against Oracle. Using sqlite3 or postgres against the same codebase works correctly.
Change History (2)
comment:1 by , 17 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [5020]) boulder-oracle-sprint: Fixed #3748.