-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fir 35103 cannot find matching fk table id for fk field #62
Fir 35103 cannot find matching fk table id for fk field #62
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from that looks good to my limited knowledge of Clojure.
(defmethod sql-jdbc.describe-table/get-table-pks :firebolt | ||
[_ ^Connection conn db-name-or-nil table] | ||
(let [table-name (get table :name) | ||
schema (get table :schema) | ||
base-sql "SELECT primary_index FROM information_schema.tables WHERE table_name = ?" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we be reporting primary index as a primary key? As far as i understand there's an important distinction - PIs are not unique.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is used primarily for reporting to a customer, I don't think metabase relies on PKs (since you can just report an empty set and it would still work).
Attemp to fix (atleast partially) the unable to find matching fk issue. A bunch of improvements + reporting FKs as not supported by Firebolt (which is true)