Since every version of the game comes with a new database, these edits must be made each time. That's a lot of tedium, and tedium is evil. Your computer is there to serve you; don't make the mistake of doing things by hand all of the time when you could have the computer do it for you.
One way to automate things is to write shell scripts. This is particularly good for automating the process of running programs. (It's a terrible way to automate the process of clicking on buttons though, so I'm glad we don't have to do that very often.)
Since it's probable that many people here are new to writing shell scripts, I'd like to offer some small examples. The sqlite3 program can take a database name followed by a SQL command to run (or multiple commands). It can even read those commands from standard input, exactly as if you had typed them in manually. Thus, we can write the SQL commands in our shell script and send them to sqlite3 to execute, like this:
#!/bin/sh
for prefix in "Fuel Storage" "Compressed Fuel Storage System" "Engineering Spaces"; do
sqlite3 AuroraDB.db <<EOF
UPDATE FCT_ShipDesignComponents
SET Name = '${prefix}'
|| (SELECT char
FROM (SELECT Size AS value,
char(8320 + row_number() OVER (ORDER BY Size)) AS char
FROM FCT_ShipDesignComponents
WHERE Name LIKE '${prefix}%')
WHERE value = Size)
|| ' ('
|| cast(Size * 50 AS integer)
|| 't)'
WHERE Name LIKE '${prefix}%';
EOF
done
I went ahead and cleaned up the query a bit; the first one worked, but it was a little bit… janky. This often happens when you're typing commands in manually. It takes more effort to polish the thing and format it nicely, so we often skip that step at first.
I should point out that we're relying on the table and field names being the same from one database version to the next. The database schema can and will change from time to time, as features are added to the game, so that could happen. Still, it seems like a safe assumption to make in this case. If they do ever change, then running this script will produce error messages, but will be harmless. It would be a simple matter to find the new names and edit the script if that happens (and even that manual action can be automated, should the need arise).
It might one day be necessary to put the old names back. Since it would be very tedious to do so by hand, I automated it like this:
#!/bin/sh
sqlite3 AuroraDB.db <<EOF
update fct_shipdesigncomponents set name = 'Fuel Storage - Fighter' where sdcomponentid = 67058;
update fct_shipdesigncomponents set name = 'Fuel Storage - Tiny' where sdcomponentid = 38117;
update fct_shipdesigncomponents set name = 'Fuel Storage - Small' where sdcomponentid = 26266;
update fct_shipdesigncomponents set name = 'Fuel Storage' where sdcomponentid = 600;
update fct_shipdesigncomponents set name = 'Fuel Storage - Large' where sdcomponentid = 43529;
update fct_shipdesigncomponents set name = 'Fuel Storage - Very Large' where sdcomponentid = 43531;
update fct_shipdesigncomponents set name = 'Fuel Storage - Ultra Large' where sdcomponentid = 43530;
update fct_shipdesigncomponents set name = 'Compressed Fuel Storage System - Small' where sdcomponentid = 65061;
update fct_shipdesigncomponents set name = 'Compressed Fuel Storage System' where sdcomponentid = 26420;
update fct_shipdesigncomponents set name = 'Compressed Fuel Storage System - Large' where sdcomponentid = 64796;
update fct_shipdesigncomponents set name = 'Compressed Fuel Storage System - Very Large' where sdcomponentid = 64797;
update fct_shipdesigncomponents set name = 'Engineering Spaces - Fighter' where sdcomponentid = 27134;
update fct_shipdesigncomponents set name = 'Engineering Spaces - Tiny' where sdcomponentid = 27133;
update fct_shipdesigncomponents set name = 'Engineering Spaces - Small' where sdcomponentid = 26267;
update fct_shipdesigncomponents set name = 'Engineering Spaces' where sdcomponentid = 25147;
EOF
This demonstrates how a single invocation of sqlite3 can execute multiple SQL commands.
I hope this little side trip into shell scripting has taught you something that you can use in your everyday life.
