Timeline for answer to SQLAlchemy default DateTime by qwerty
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2019 at 10:06 | history | edited | taras | CC BY-SA 4.0 |
code format
|
| Jun 23, 2016 at 1:45 | comment | added | ChaimG | @self, From the documentation: "If True, and supported by the backend, will produce ‘TIMESTAMP WITH TIMEZONE’. For backends that don’t support timezone aware timestamps, has no effect. . | |
| Jun 23, 2016 at 1:41 | comment | added | ChaimG |
What does timezone=True do?
|
|
| Mar 15, 2016 at 22:25 | comment | added | Kris Hardy | @Metalstorm No, this is correct. sqlalchemy.sql.func is a special case that returns a sqlalchemy.sql.functions.now instance, not the current time. docs.sqlalchemy.org/en/latest/core/… | |
| Feb 26, 2016 at 1:27 | comment | added | Metalstorm | Isn't func.now() executed when the descriptor is defined, so all models/children (if this is a base class) will have the same DT value. By passing in a function reference like 'datetime.datetime.utcnow' it is executed separately for each. This is crucial for 'created' or 'updated' properties. | |
| Jun 6, 2015 at 14:55 | comment | added | rgtk |
You can also use server_default instead of default so value will by handled by database itself.
|
|
| May 6, 2015 at 17:17 | history | answered | qwerty | CC BY-SA 3.0 |