dina-web-nrm / mediaserver-module Goto Github PK

"The directories range from '0' to 'F' (hexadecimal) with a depth of 3 layers, which results in 4096 directories ( 16^3 ). To illustrate, 10 000 000 (ten million) mediafiles would be, with an even spread, would be divided into 2441 mediafiles per directory."

Suggest each directory going from 00-ff (256), as modern Linux file systems can handle this number of directories no problem. And suggest depth of 5, as the example of 10m media files is not a large amount for many sites.
The example for ab30899c-58a0-4305-85a6-bbfa14f89b92 would now be:
ab/30/89/9c/58/a0430585a6bbfa14f89b92

Also, do not store the dashes in the UUID: they are only inserted to make it easier for humans to read. Also suggest not using them in URLs, etc.

OK, multiple issues, my bad.

How difficult would it to modify to allow SQLite3 backend instead of MySql? Advantage is that a site would not need to have a MySql server instance running.

All 128bit UUIDs in hex are 32 chars long:
ab30899c58a0430585a6bbfa14f89b92

So it is a fixed length field.

In https://github.com/DINA-Web/mediaserver-module/blob/master/db/src/main/dbschema/db.changelog-0.5.xml for various tables (MEDIA, IMAGE, SOUND, VIDEO, etc) is defined as:
<column name="UUID" type="varchar(255)" autoIncrement="false">
I think it should be
<column name="UUID" type="char(32)" autoIncrement="false">