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

Schema.qm: AbstractSchema::checkExistence() is broken by design #3266

Closed
pvanek opened this issue Jan 18, 2019 · 0 comments
Closed

Schema.qm: AbstractSchema::checkExistence() is broken by design #3266

pvanek opened this issue Jan 18, 2019 · 0 comments
Assignees
Milestone

Comments

@pvanek
Copy link
Contributor

@pvanek pvanek commented Jan 18, 2019

the firstKey approach fail if somebody add a non-existing table at the 1st place in the list

@pvanek pvanek added this to the 0.9 milestone Jan 18, 2019
@pvanek pvanek self-assigned this Jan 18, 2019
pvanek pushed a commit that referenced this issue Jan 18, 2019
…esign. It could report wrong result in some cases
pvanek pushed a commit that referenced this issue Jan 18, 2019
…esign. It could report wrong result in some cases
pvanek pushed a commit that referenced this issue Jan 18, 2019
…esign. It could report wrong result in some cases
davidnich added a commit that referenced this issue Jan 18, 2019
… sequence retrieval
davidnich added a commit that referenced this issue Jan 18, 2019
#3267)

* refs #3266 Schema.qm: AbstractSchema::checkExistence() is broken by design. It could report wrong result in some cases

* refs #3266 fixed schema alignment with freetds / SQL server by fixing sequence retrieval
@davidnich davidnich closed this Jan 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants