Details for the issue
What did you do?
create a SQL script to update some entries:
Update WindowsLoginNames
Set extension = '1'
Where extension = "";
saved as "update blank extensions.sql"
created a shortcut on desktop:
"C:\Program Files\DB Browser for SQLite\DB Browser for SQLite.exe" -s "update blank extensions.sql" -q WSCConfig.db
set to run run C:\LTR\Config (where the database is located)
What did you expect to see?
script should run and update the values, then quit
What did you see instead?
Does not make any changes. If the "-q" is removed, the script runs - but does not save changes to the database. If I edit the script to add a "COMMIT" command as follows:
Update WindowsLoginNames
Set extension = '1'
Where extension = "";
COMMIT;
it still does not work if the -q option is specified. But if I remove that and run it again, the changes ARE then saved.
Useful extra information
DB4S v3.13.1 [built for x86_64-little_endian-llp64] on Windows Server 2016 Version 1809 (winnt/10.0.17763) [x86_64]
using SQLite Version 3.46.1
and Qt 5.15.2
Details for the issue
What did you do?
create a SQL script to update some entries:
Update WindowsLoginNames
Set extension = '1'
Where extension = "";
saved as "update blank extensions.sql"
created a shortcut on desktop:
"C:\Program Files\DB Browser for SQLite\DB Browser for SQLite.exe" -s "update blank extensions.sql" -q WSCConfig.db
set to run run C:\LTR\Config (where the database is located)
What did you expect to see?
script should run and update the values, then quit
What did you see instead?
Does not make any changes. If the "-q" is removed, the script runs - but does not save changes to the database. If I edit the script to add a "COMMIT" command as follows:
Update WindowsLoginNames
Set extension = '1'
Where extension = "";
COMMIT;
it still does not work if the -q option is specified. But if I remove that and run it again, the changes ARE then saved.
Useful extra information