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

Error codes should be consistent for different operations [CORE3112] #3490

Open
firebird-automations opened this issue Aug 20, 2010 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @aafemt

Attempt to SELECT from non-existing table produces error code 335544580, but attempt to drop non-existing table produces not documented code 336397206.

@firebird-automations
Copy link
Collaborator Author

Modified by: @aafemt

issuetype: Improvement [ 4 ] => Bug [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

1) Hum, undocumented? const ISC_STATUS isc_dsql_table_not_found = 336397206L;
2) Completelly different errors should produce the same code?
3) Do you missed proposed and implemented in HEAD new DDL error codes?

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

1) Sources are not a documentation.
2) They are not different, they are the same - "table (or other object) does not exists".
3) Yes, I've missed them. Point me to their descriptions, please.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Read thread "DDL exceptions", but it's not very related to this ticket, sorry.

Ok, you're correct about 2. And there is much more duplicate codes from DYN and DSQL subsystems.

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

And these duplicate codes is exactly the bug which this ticket is about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant