-
Notifications
You must be signed in to change notification settings - Fork 8
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
[defog
] Postgres table name format.
#9
Open
JeevansSP
wants to merge
5
commits into
defog-ai:main
Choose a base branch
from
JeevansSP:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+13
−5
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -227,22 +227,30 @@ def generate_postgres_schema(self, tables: list, upload: bool = True) -> str: | |
cur.execute( | ||
"SELECT table_name FROM information_schema.tables WHERE table_schema = 'public';" | ||
) | ||
tables = [row[0] for row in cur.fetchall()] | ||
tables = [f"public.{row[0]}" for row in cur.fetchall()] | ||
else: | ||
for table in tables: | ||
if not table or len(table.split("."))!=2: | ||
raise ValueError(f"PostgreSQL table names should be of the following format <schema>.<table> which is violated by '{table}`") | ||
|
||
print("Retrieved the following tables:") | ||
|
||
for t in tables: | ||
print(f"\t{t}") | ||
|
||
print("Getting schema for each table in your database...") | ||
# get the schema for each table | ||
for table_name in tables: | ||
for table in tables: | ||
|
||
schema,table_name = table.split(".") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To avoid needing to throw an exception, one suggestion is to first check if there is a for table in tables:
if '.' in table:
schema, table_name = table.split(".",1)
else:
schema, table_name = "public", table |
||
cur.execute( | ||
"SELECT CAST(column_name AS TEXT), CAST(data_type AS TEXT) FROM information_schema.columns WHERE table_name::text = %s;", | ||
(table_name,), | ||
"SELECT CAST(column_name AS TEXT), CAST(data_type AS TEXT) FROM information_schema.columns WHERE table_name::text = %s and table_schema::text = %s;", | ||
(table_name, schema), | ||
) | ||
rows = cur.fetchall() | ||
rows = [row for row in rows] | ||
rows = [{"column_name": i[0], "data_type": i[1]} for i in rows] | ||
schemas[table_name] = rows | ||
schemas[table] = rows | ||
|
||
# get foreign key relationships | ||
print("Getting foreign keys for each table in your database...") | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It might not be a good idea to raise an exception here if users just pass us their table names without schema (for backward compatibility purposes). Could we default to the current logic of working with table names directly when no schema is provided (ie not raise an exception)?
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.
While I agree with backward compatibility
The problem arises in these two sql queries
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.
Also the exception is raised only if the provided tables to generate the schema does not contain scheme prefixed
when no table names are provided then it defaults to using the tables from the
public
schemaThere 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.
Thanks for updating this. A number of our customers rely on just passing in the table names (without schema) and we can't raise an exception here.