A tool for downloading and analysing server info from OriginsRO
King_DuckZ
80ef2afbee
This works in a much simpler way than the items table. Here we just upsert new values, with the unique constraint on the internal item_id (not the upstream one, which is never entered into this table). This should mean that if an item from the items table with eg: item_id=501,id=9 gets marked as deleted and re-entered as item_id=501,id=5000, then icon with item_id=9 should remain in the table (there is no delete ever), and a new one with item_id=5000 gets added. Originally they both referred to item 501 and they still do, but because of how the items table now works, icons should also benefit and historical data should remain in the face of upstream changes. |
||
|---|---|---|
| sample_responses | ||
| src | ||
| subprojects | ||
| .gitignore | ||
| .gitmodules | ||
| COPYING | ||
| example.c | ||
| meson.build | ||
| meson_options.txt | ||
| orotool.conf | ||