VDatabase Mode
On database creation you may specify one of the following alternatives to control how many files a database will have and how data will be organized in these files:
kDscDatBlbInd = 1 //".vdb"[description, data, BLOB, indexes] kDsc_DatBlbInd = 2 //".vdb"[description] + ".dat"[ data, BLOB, indexes] kDsc_DatBlb_Ind = 3 //".vdb"[description] + ".dat"[data, BLOB] + ".ind"[indexes] kDsc_Dat_Blb_Ind = 4 //".vdb"[description] + ".dat"[data] + ".blb"[BLOB] + ".ind"[indexes] kDscDatBlb_Ind = 5 //".vdb"[description,data,BLOB] + ".ind"[indexes] kDscDat_Blb_Ind = 6 //".vdb"[description,data] + ".blb"[BLOB] + ".ind"[indexes] kDscDatInd_Blb = 7 //".vdb"[description,data,indexes] + ".blb"[BLOB] kDsc_DatInd_Blb = 8 //".vdb"[description] + ".dat"[data,indexes] + ".blb"[BLOB]
Choosing a Mode
- Many MacOS developers prefer the first mode. It is convenient for users because contains all information in the single file.
- If you choose the mode where .vdb volume is created separately then you get ability to create a new empty database easy. For this you have to copy .vdb volume into another location and open it. Valentina will automatically create rest necessary files.
- If you choose the mode where .ind volume is created separately then you can re-build easy all indexes. For this you have to delete an index file and open a database once again. Valentina will automatically build all necessary indexes.
- Nowadays a separate .blb volume has no significant advantages. In the past, when many OS had a limit on a file size in 2 GB, a separate .blb volume allowed to increase the value of stored data up to 4 GB (2 GB in the .dat file and 2 GB in the .blb file).