Skip to content
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

SNOW-922868: Preserve the sequence order of foreign keys when dealing with composite keys. #450

Open
skp33 opened this issue Sep 25, 2023 · 1 comment
Labels
bug Something isn't working status-triage_done Initial triage done, will be further handled by the driver team

Comments

@skp33
Copy link

skp33 commented Sep 25, 2023

Hi Team,

I am encountering issues while working with composite foreign keys. For every version, I am receiving fixed create_foreign_key and drop_constraint operations. Upon debugging, I discovered that we are not preserving the sequence order of foreign keys when comparing with metadata.

For more detail, I am pointing out the specific code snippet that requires modification. - https://github.com/snowflakedb/snowflake-sqlalchemy/blob/main/src/snowflake/sqlalchemy/snowdialect.py#L414-L434C18

@skp33 skp33 added bug Something isn't working needs triage labels Sep 25, 2023
@github-actions github-actions bot changed the title Preserve the sequence order of foreign keys when dealing with composite keys. SNOW-922868: Preserve the sequence order of foreign keys when dealing with composite keys. Sep 25, 2023
@sfc-gh-dszmolka sfc-gh-dszmolka added status-triage_done Initial triage done, will be further handled by the driver team and removed needs triage labels Dec 11, 2024
@sfc-gh-dszmolka
Copy link
Contributor

hi - apologies for not being able to pick this up earlier. we'll take a look. also appreciate the PR proposal!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

2 participants