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
In order to save time it would be great to either specify a number of possible DBMS like --dbms=postgres,Oracle or maybe to exclude certain DBS like --dbms='!postgres' or --dbms='!postgres,!Oracle' (or with sth like --notdbms=postgres,Oracle).
At least from my experience often I either know the architecture but don't have a clue in which DB which parameter ends up. In other cases I know that for sure it is not IBM DB2, Informix, Microsoft Access, MSSQL etc.
The text was updated successfully, but these errors were encountered:
--dbms already worked that way, then some users misused it (not on purpose) and I unknowingly turned off that feature (multiple DBMS statement). Will patch accordingly
With latest revision, something like (your first proposition) --dbms=postgres,Oracle will restrict all tests to ONLY PostgreSQL and Oracle. Haven't implemented ! logic as I believe that it wouldn't be used as much.
In order to save time it would be great to either specify a number of possible DBMS like
--dbms=postgres,Oracle
or maybe to exclude certain DBS like--dbms='!postgres'
or--dbms='!postgres,!Oracle'
(or with sth like--notdbms=postgres,Oracle
).At least from my experience often I either know the architecture but don't have a clue in which DB which parameter ends up. In other cases I know that for sure it is not
IBM DB2, Informix, Microsoft Access, MSSQL
etc.The text was updated successfully, but these errors were encountered: