patrickTingen
Automatically select a table derived from the query
When I'm viewing a table and I enter a query for an unrelated table the query fails. I was wondering if it's possible to derive the table from this query and automatically select te correct table and execute the query.
Eg when I'm viewing table1 and I enter in the query: table2.field = "X" the underlying query will be faulty: for each table1 where (table2.field = "X") no-lock
Seeing as this is never correct, might as well automatically switch to table2 and execute the query.
Also, I think this might save some time as in the user doesn't need to select the table anymore but can start typing straight away.
Hi Steven,
Thanks for using DataDigger and thatnks for submitting this idea. Actually, I find it a nice idea and I will add it to my list of features to implement. Currently I am working on a large refactoring; I will see if I can implement this together with that. Thanks!
Best regards Patrick Tingen
Op do 26 jan. 2023 om 15:51 schreef Steven Peeters @.***
:
When I'm viewing a table and I enter a query for an unrelated table the query fails. I was wondering if it's possible to derive the table from this query and automatically select te correct table and execute the query.
Eg when I'm viewing table1 and I enter in the query: table2.field = "X" the underlying query will be faulty: for each table1 where (table2.field = "X") no-lock
Seeing as this is never correct, might as well automatically switch to table2 and execute the query.
Also, I think this might save some time as in the user doesn't need to select the table anymore but can start typing straight away.
— Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/99, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHPV2TA7NNC5D2JA6P3WUKFPDANCNFSM6AAAAAAUHS2I4M . You are receiving this because you are subscribed to this thread.Message ID: @.***>
