mORMot Open Source

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 13,165

Website

Why Big Table?

  What are these classes meant for?
  - add a simple storage and data persistence to your application, in a few KB of code
  - store thunmbails of pictures which content is not intented to change often
  - cache a huge quantity of generated HTML or XML pages, or their compressed version
  - implement a logging or read/only audit trail mechanism into your application
  - store settings in an handy way (TSynBigTableString is a good .INI replacement)
  - access to compressed data on a CD-ROM or DVD-ROM (see our Open Source compression libraries in our web site) - you can even add items to the list, since they will remain in memory; but they will be lost when you close the file
  - have an easy way to share data between Delphi 7 and Delphi 2010 applications, without any Unicode / TStringList encoding headache
  - store external resource files (think about an hidden folder) in which you can write
  - if you don't want to install a database engine and configure it
  - if you need speed and performance
  - if you don't want to reinvent the wheel
  - etc... etc...

  What are these classes NOT for?
  - interact with DBExpress or VCL database components
  - replacing NTFS - go to Linux and pick the right file system you need
  - storing hierarchical data (like directories) - use B-Tree and such instead
  - store huge data items (maximum is 2 GB for one item) - a few MB is good, but remember that data is stored into RAM before writting to disk
  - replace a SQL database engine - use our SQLite3 framework instead, see http://synopse.info/forum/viewforum.php?id=2
  - save your soul or make me rich

eraldo

Member

From: Brasil

Registered: 2010-07-22

Posts: 68

Website

Re: Why Big Table?

Big Table will have long life?
Even with the notable features of the double Mormot + Sqlite?