-
Notifications
You must be signed in to change notification settings - Fork 33
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: googleapis/python-spanner-sqlalchemy
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.13.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: googleapis/python-spanner-sqlalchemy
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.14.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 10 files changed
- 4 contributors
Commits on Jun 27, 2025
-
Configuration menu - View commit details
-
Copy full SHA for a50e4fa - Browse repository at this point
Copy the full SHA a50e4faView commit details -
Configuration menu - View commit details
-
Copy full SHA for af79305 - Browse repository at this point
Copy the full SHA af79305View commit details -
Configuration menu - View commit details
-
Copy full SHA for bcb8144 - Browse repository at this point
Copy the full SHA bcb8144View commit details -
feat: Support Server-Side Checks for Enums (#694)
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 allows SQLAlchemy to generate check constraints to enforce the enum values if the create_constraint=True flag is passed to the Enum constructor. Fixes: #686Configuration menu - View commit details
-
Copy full SHA for 17e3aba - Browse repository at this point
Copy the full SHA 17e3abaView commit details -
feat: support commit timestamp option (#697)
* feat: support commit timestamp option Add support for columns with commit timestamps: https://cloud.google.com/spanner/docs/commit-timestamp Fixes: #695 * chore: use Singer in sample --------- Co-authored-by: Knut Olav Løite <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 82bb8ed - Browse repository at this point
Copy the full SHA 82bb8edView commit details -
bug: don't rollback non-spanner connections on reset (#709)
This is the simplest way to address bug #706 and address the `AttributeError: 'Connection' object has no attribute 'rollback'` I'm seeing when connections from BigQuery engines get caught by this event handler. I think we should be able to rely on SQLAlchemy's [reset on return](https://docs.sqlalchemy.org/en/20/core/pooling.html#reset-on-return) behaviour to rollback transactions when they're reset rather than call rollback ourselves. That behaviour is also something end users can configure, so it'd be good to respect their settings if they disable the behaviour. Fixes: #706
Configuration menu - View commit details
-
Copy full SHA for 4f86eb3 - Browse repository at this point
Copy the full SHA 4f86eb3View commit details -
chore(main): release 1.14.0 (#710)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 170379f - Browse repository at this point
Copy the full SHA 170379fView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.13.1...v1.14.0