Programming

In that case, it might make sense for you to use the OS as your database. Divide your tables/rows in some manner and create a hashed directory scheme to save them. So for instance, tables with a 64-bit index that in hex looks something like: "0a924b233f2917fa" would be stored in the directory:

Code:

0a/92/4b/23/3f/29/17/fa

with the fields as files. Or the entire table can be a file (the last path element).

Either way, table management becomes a bit easier, and the OS handles the efficient management of data location and juggling. All you have to do is keep track of how many files can in be in memory at once. But again, can let the OS do that for you, since it will buffer files very efficiently.

To be honest, I don't understand what you mean and how I should apply your suggestion to my case (for dumping the tables).

If possible, can you point to any interesting lecture with actual examples of what you are talking about? Or at least the keywords to use with Google? :-)

Thanks again for your time and your help!

Regards,
S.

I spent a few minutes on Google. Maybe this will help:

On Hashed directories: Hashed directory creation for storing thousands of images on file system | drupal.org and Directory Hashing Algorithm

On Flat files and various implementations: Flat file database - Wikipedia, the free encyclopedia

Discussions on using flat-file databases for real-world applications:

Storing Data with PHP — Flat File or Database? - For Dummies

Viaweb FAQ

Do You Believe in a Flat-File Driven Content Management System?

https://salempress.com/Store/samples...nformatics.htm