Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

feat: Support Server-Side Checks for Enums #694

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
Loading
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion 8 google/cloud/sqlalchemy_spanner/sqlalchemy_spanner.py
Original file line number Diff line number Diff line change
Expand Up @@ -798,10 +798,16 @@ class SpannerDialect(DefaultDialect):
supports_sequences = True
sequences_optional = False
supports_identity_columns = True
supports_native_enum = True
supports_native_boolean = True
supports_native_decimal = True
supports_statement_cache = True
# Spanner uses protos for enums. Creating a column like
# Column("an_enum", Enum("A", "B", "C")) will result in a String
# column. Setting supports_native_enum to False means SQLAlchemy
# will generate check constraints to enforce the enum values
# server-side rather than rely on a the database's native enum
# type to enforce them.
supports_native_enum = False

postfetch_lastrowid = False
insert_returning = True
Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.