No constrained columns if no primary key#4
Closed
elconde wants to merge 1 commit intosqlanywhere:masterfrom
Closed
No constrained columns if no primary key#4elconde wants to merge 1 commit intosqlanywhere:masterfrom
elconde wants to merge 1 commit intosqlanywhere:masterfrom
Conversation
|
We are working at getting a CLA in place to be able to accept pull requests. |
Contributor
|
This change has not been merged, but an equivalent change has been added to version 1.0.3. |
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
3 participants
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.
Hello,
We've been using this dialect for a few months on a project to read data from SQL Anywhere. The database is provided by a vendor, so we cannot modify it. They give us views which don't have primary keys. We found that, even though reflecting views is supported in SQLAlchemy, we could not reflect the database because of the lack of primary keys.
Adding this snippet seems to have fixed our issue. We've been running the integration for months now. I have no idea if this is correct, but it works! We're only reading, not writing to the database, so I couldn't say what implications this might have for writing.
I should also mention that we are using sqlalchemy.ext.declarative.DeferredReflection as our "base" class and adding primary keys to each class.
I hope it helps!
Regards,
Robert Conde