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
INFORMATION_SCHEMA [CORE737] #1112
Comments
Modified by: @pcisarWorkflow: jira [ 10761 ] => Firebird [ 15164 ] |
Commented by: Pabloj (pabloj_sourceforge) Could be provided as a set of views |
Commented by: Ivan (patuljak) please support all statistics in INFORMATION_SCHEMA size of tables, size of index etc... on easy way. |
Hello It appears Firebird does not support information_schema while it would be great to follow the norm. i would add, it does not require a lot of job to produce an information_schema schema and then some views in it. Best regards, Simon |
But adding support of schemas themselves is quite a lot of work. |
@aafemt Thanks for your answer, guess I'm not the only one working on a saturday evening ^^. I thought you had most in RDB$ and then it would be a matter of a few hours to build the views based on RDB$. Am I wrong ? O_o Best regards, Simon |
I repeat: the views is not a problem. Lack of schemas is. Reusing of RDB.RELATIONS.RDB$OWNER as a schema name is quite reasonable decision. Feel free to prepare RFC for all that and share it in devel mail-list. |
The problem is not with adding the views themselves (I believe someone in the past already made a script to define them), the problem is that INFORMATION_SCHEMA is supposed to be a separate schema in the database, and Firebird doesn't have schemas. Adding this now without schema support in Firebird would introduce backward compatibility issues once schemas are added. And no, |
@aafemt @mrotteveel Thanks for the clarification, I had misunderstood it at first. Get it. |
Submitted by: german666 (german666)
Votes: 7
SFID: 1468113#
Submitted By: german666
SQL STANDARD INFORMATION_SCHEMA
THANKS.
The text was updated successfully, but these errors were encountered: