You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is comon that people execute cql files against the DB.
Allow users to select a file containing lots of CQL statements to execute against the DB and run against the DB.
This is essentially a very large multi-statment query like we run in the enhanced console. What we should do here is essentially pipe the CQL file into our enhanced cql statement prompt and execute the statments as BAU.
We should expose this via Right Click on a cluster and execute the selected CQL file.
Also add it somewhere near the CQL prompt area.
When running the CQL file users should also have the ability to terminate its execution.
The CQL history for this action should be a pointer to the file as the number of statments could be very high. If they click onto the cql file, in the history we should open the file in the CQL view (the one we use for looking at schemas etc..). Make sure the UX show its a CQL file being looked at in a prominent fashion.
Note - this file could be very large e.g lots of create statments and inserts to populate a DB. Test this with large files with 1000s of DML statements and various DDLs and make sure to test batch statments in the CQL file.
The text was updated successfully, but these errors were encountered:
It is comon that people execute cql files against the DB.
Allow users to select a file containing lots of CQL statements to execute against the DB and run against the DB.
This is essentially a very large multi-statment query like we run in the enhanced console. What we should do here is essentially pipe the CQL file into our enhanced cql statement prompt and execute the statments as BAU.
We should expose this via Right Click on a cluster and execute the selected CQL file.
Also add it somewhere near the CQL prompt area.
When running the CQL file users should also have the ability to terminate its execution.
The CQL history for this action should be a pointer to the file as the number of statments could be very high. If they click onto the cql file, in the history we should open the file in the CQL view (the one we use for looking at schemas etc..). Make sure the UX show its a CQL file being looked at in a prominent fashion.
Note - this file could be very large e.g lots of create statments and inserts to populate a DB. Test this with large files with 1000s of DML statements and various DDLs and make sure to test batch statments in the CQL file.
The text was updated successfully, but these errors were encountered: