Open hennlo opened 1 year ago
@hennlo is the expected result is to prevent user to input * right?
@EslamAsHhraf No actually what you're describing is another issue: #447 that shall prevent any *
from beeing rendered and executed because it currently breaks the schema.
This is issue is the successor to the first issue if you will so. Becaase at the end I want to add different tables all at once without having to specify each one individually. This issue is a little bit more advanced compared to the first one, because you need to add functionality to read the schema, detect all possibilities and subsequently add them to Polypheny.
But again if you want to work on prohibitting users to input *
#447 is the issue for you.
Hi! can u assign me this issue and issue #447 and I believe i can solve them as they appear related .
Hii so we need to implement a feature in which if we add xyz* all the tables startung with xyz must be added here do we need to change only ui or the backend logic?
Affected Areas
DB, UI
Feature Description
When adding new Data Sources we currently only have the option to add tables, views by explicitly adding them name by name.
However, for larger projects this is impractical and tedious. Instead allow adding multiple tables by creating a FLAG to add all tables or allow wildcard specification using an asterix
*
to add all tables this user has access to for each schema.This could also allow "blacklisting" some tables that should explicitly not be added.
Use Case(s)
This is related to Bug: #447 Intuitively it should work to add multiple tables at once , without specifying them one by one.
Possible Solutions
Extend SQL Syntax for system management to allow wildcards instead of specifying table by table. Add possibility in UI to retrieve multiple tables at once. via wildcard or FLAG
Possible Alternatives
Add Data Sources only as connection objects and then in a separate step, create virtual/remote entities referencing to a source table via that connection.
That decouples the source creation from the virtual table creation.
This would also simplify "refreshing" definitions of existing data sources without really recreating them.