Difference between revisions of "Relational database comparison"

From Gramps
Jump to: navigation, search
m
m
Line 1: Line 1:
This page if for a comparison of different database, and is specific for how they might be used for GRAMPS. It was started to help with GEPS 010: SQL Backend.  
+
This page if for a comparison of different database, and is specific for how they might be used for GRAMPS. It was started to help with [[GEPS 010: SQL Backend]].  
  
 
=SQLite=
 
=SQLite=

Revision as of 17:40, 26 March 2009

This page if for a comparison of different database, and is specific for how they might be used for GRAMPS. It was started to help with GEPS 010: SQL Backend.

SQLite

Advantages

  • far easier to setup. just start writing to the file! no connection or user accounts.
  • smaller install (code) size.
  • easier for users to manage / and share sepperate db's
  • single file
  • good support.

Disadvantages

  • while great for what it is it's not an enterprise level database
  • many "traditional" relational db things are lacking.
  • while tools exist they aren't as fleshed out and solid as the mysql ones.


MySQL

Advantages

  • far better tools for management and reporting
  • a true enterprise level database capable of handling serious loads
  • far more is built into the db. ie auto incrementing fields, stored procedures and on and on.
(sqlite may not even have triggers but I can't remember)
  • far more extensive user base and support.

Disadvantages

  • install size (bloat)
  • an actual server to setup run and maintain.
    • there are tools that can do this automatically though and make things almost none
existent for an end user. also the embeddable mysql might be an option.
  • may be difficult to manage / share multiple databases. more difficult but very do able.
 maybe not even that difficult. it would just take some planning.