-
Notifications
You must be signed in to change notification settings - Fork 323
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
Save a DB_Table
as a data link
#11295
Comments
Radosław Waśko reports a new STANDUP for yesterday (2024-10-17): Progress: Working on saving queries. Thinking what to do with prepared statement interpolations. Implemented serialization of SQL_Statement and tests for it. Updated datalink schema. It should be finished by 2024-10-21. Next Day: Next day I will be working on the same task. Add logic for constructing a table from SQL Statement, deserializing tables in data links. Add tests. |
Radosław Waśko reports a new STANDUP for the provided date (2024-10-18): Progress: Working on constructing table from SQL and integrating that with datalinks (parsing etc.). Simplifying datalink logic to single constructor. It should be finished by 2024-10-21. Next Day: Next day I will be working on the same task. Add tests for Postgres, update other datalinks too and enable tests. |
Radosław Waśko reports a new STANDUP for today (2024-10-21): Progress: Added tests, finished implementation. Added feature detecting temporary tables in data link and warning about them. Put up the PR. It should be finished by 2024-10-21. Next Day: Next day I will be working on the #9812 task. Switch to types work for a bit. |
Radosław Waśko reports a new STANDUP for yesterday (2024-10-22): Progress: Fixing some remaining test failures on the PR. Reviews. Picking up work on types. It should be finished by 2024-10-22. Next Day: Next day I will be working on the #9812 task. Investigate not resolved extension methods. |
Similarly to #11294, we want to be able to save a specific
DB_Table
as a data link.This should create a data link that will connect to the same database and then read the query that the
DB_Table.to_sql
returns, and reconstruct theDB_Table
view (although it will have a different underlying structure - instead of all the IR used to construct the query it will just contain the SQL code usingFrom_Spec.Query
).This behaves essentially like storing a
VIEW
for the query represented by theDB_Table
.If the underlying connection does not support saving as data link (e.g. SQLite), it should raise a user-friendly error.
The text was updated successfully, but these errors were encountered: