Rought database engine comparison

 

MySQL SQLite DB Engine / Flat File Databases File system
 
pros      
  • can manage big databases
  • can manage fairly big databases
  • database is a file on the web server
  • easier to backup
  • can manage small databases
  • database is a directory on the web server
  • easy to set-up
  • easy to manage (.tsv file : Excel)
  • easy to backup
  • functions or methods only
  • can be easy to set-up
  • can be easy to manage
  • easy to backup
  • functions only
 
cons
  • needs a database server
  • difficult to set-up
  • difficult to manage
  • difficult to backup
  • I don't like SQL...
  • difficult to set-up
  • difficult to manage
  • I don't like SQL...
  • for small databases only
  • needs boring coding
  • for small databases only

 

For small applications, Flat File Databases can be the best solution.

 

 

Compare to other Flat File Databases, DB Engine has some significant avantages:

  • Can work simultaneously on several databases
  • A table can belong to more than one database
     
  • Small: only one file to include (20Kb (5Kb zipped) with comprehensive functions and variables names)
  • Include file for debug functions: table list and dump
     
  • Complete set of functions to fullfill most needs
  • Object programing
     
  • Where clauses
  • Sort orders on fields
  • Table joints can be used in Field lists (fetch), Where clauses and Sorts.
     
  • Enhanced file locking system with random and exponential delays
  • Lock / unlock of a list of tables
     
  • Cache to speed up operations
  • Can work on large files
  • Usage of field names
     
  • Log file to monitor file locking system (retries, fails...)
  • Debug mode to display run-time warnings
     
  • fastFetch and fastUpdate functions for loaded contexts
  • Auto-increment fields for insert

 

 

» Reference