chore: emulate oid data type with hash function#4277
Merged
olavloite merged 1 commit intopostgresql-dialectfrom Apr 2, 2026
Merged
chore: emulate oid data type with hash function#4277olavloite merged 1 commit intopostgresql-dialectfrom
olavloite merged 1 commit intopostgresql-dialectfrom
Conversation
037290e to
b2b1b94
Compare
Use the farm_fingerprint function to emulate the oid of tables, instead of using the table name directly. This ensures that the data type that is being returned is an int, which is much more like the original oid data type. Towards #4276
rayudu3745
reviewed
Apr 1, 2026
src/main/java/com/google/cloud/spanner/pgadapter/statements/PgCatalog.java
Show resolved
Hide resolved
rayudu3745
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use the farm_fingerprint function to emulate the oid of tables, instead of using the table name directly. This ensures that the data type that is being returned is an int, which is much more like the original oid data type.
Towards #4276