-
Notifications
You must be signed in to change notification settings - Fork 2
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
SQLAlchemy/DDL: Support server_default
column definition option
#106
Comments
amotl
changed the title
Check how
Honor SQLAlchemy's Oct 6, 2022
RETURNING
is fiddled back through SQLAlchemyserver_default
option
amotl
changed the title
Honor SQLAlchemy's
Honor SQLAlchemy's Oct 6, 2022
server_default
optionserver_default
column definition option
amotl
changed the title
Honor SQLAlchemy's
SQLAlchemy: Honor Mar 6, 2023
server_default
column definition optionserver_default
column definition option
amotl
changed the title
SQLAlchemy: Honor
SQLAlchemy/DDL: Support Mar 6, 2023
server_default
column definition optionserver_default
column definition option
JanLikar
referenced
this issue
in JanLikar/crate-python
May 26, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Although some implementations quote the values passed to `server_default`, we don't do that here, to stay in line with SA docs. Fix #454.
JanLikar
referenced
this issue
in JanLikar/crate-python
May 26, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
1 task
JanLikar
referenced
this issue
in JanLikar/crate-python
May 31, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
JanLikar
referenced
this issue
in JanLikar/crate-python
Jun 5, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
JanLikar
referenced
this issue
in JanLikar/crate-python
Jun 8, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
JanLikar
referenced
this issue
in JanLikar/crate-python
Jun 8, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
JanLikar
referenced
this issue
in JanLikar/crate-python
Jun 8, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
amotl
referenced
this issue
in crate/crate-python
Jun 9, 2023
CrateDB's SQLAlchemy dialect now handles the `server_default` when generating table DDL. Fix #454.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Introduction
CrateDB can use functions to generate server-side default values on columns. For example, the
NOW()
function can be used to auto-generate timestamp values.Objective
It would be sweet if we could make the CrateDB SQLAlchemy dialect support this feature appropriately.
Proposal
I think the right way is to implement the official SQLAlchemy column definition option
server_default
.-- https://docs.sqlalchemy.org/en/20/core/metadata.html#sqlalchemy.schema.Column.params.server_default
Example
The collab/sa-column-server-default branch has a corresponding example program.
The text was updated successfully, but these errors were encountered: