Cache files via SQLite

[logue]

Evolve the file list output function and save it with SQLite. Main use is cache.

• The PSO2 part and the NGS part are managed separately as before.
• Prepare a table that contains the file name, the last modification date and time of the file, and the md5 hash in the parent table, and a child table that stores the contents of the file, and save them in a 1:Many relationship.
• Due to the SQLite specifications, there is not much merit in managing IDs with numbers, so UUIDs are used for primary keys. Currently, it is treated as Homebrew, so sharing sqlite files with others is not considered.

erDiagram

files {
  string id
  string name 
  integer format
  string hash
  datetime updated_at
}

contents {
  string id
  string file_id
  string name
}

files ||--|{ contents: ""

Loading

[logue]

The file name should be the path from the data directory.

For example, the data on the pso2 side will have a name like win32\0000ad8daf393f31da0fd7e26829c819, and the data on the PSO2NGS side will have a name like win32reboot\00\00ad8daf393f31da0fd7e26829c819.