Recommended: Something that uses SQL but isn't as large as standalone SQL database servers.
Personally, I wouldn't start a new project and use anything in this category. It's just a binary key-value (hashtable) blob storage mechanism, using a well-understood binary file format. Does that make it a database, in your view? Because it's not a relational database, and doesn't do SQL. Something that isn't a full SQL database, but more of a key-value store, would technically not be a flat file, but it does provide a single "key+value" list, that is quickly searchable on a single primary key. You don't want to use a full SQL database, and you think that a plain text file is too simple. Also consider using the RTree virtual table of SQLite3, which is dedicated to speed up access to double min/max multi-dimensional data: it may speed up a lot your requests. Sometimes, using additional values (like temporary sums or means) to the data is a good idea. It's a bad idea to read all file content for every request: you should better structure your data so that a single SQL query would be able to return the expended results. Update: If you plan to use SQLite, you should first guess how the data will be stored, which indexes are to be created, and how a SQL query may speed up your requests. More than 600 pages, with details of every class method, and new enhanced general introduction. I've just updated the documentation of the framework. With full Source code, working from Delphi 6 up to XE.
Synopse Big Table to store huge amount of data - see in particular the TSynBigTableRecord class to store an unlimited number of records with fields, including indexes if needed - it will definitively be faster and use less disk size than any other regular SQL DB.If you don't want to reinvent the wheel, you may find all needed Open Source tools for your task from our side:
0 kommentar(er)
