sloecode-dev team mailing list archive

[Thomi Richards <thomir@xxxxxxxxx>]

Hi Guy,

First, sorry for the late response - I've been enjoying the good weather on
Stewart Island.

You're probably better off asking the SQLite guys about the limitation of
the SQLite DBMS. However, I can say that sloecode really isn't a database
intensive application, and that we've run a SQLite database in a production
environment with around 25 student accounts without any issues. Obviously
SQLite doesn't provide any kind of replication, so My gut feeling (based on
no research at all) is that SQLite is easier to manage (it's just a file -
easy to backup etc), and unless you have good reason to want MySQL, stick
with SQLite.

If you run into any problemns, please let us know, so we can advice the
next person better.

Cheers!

On 21 December 2011 13:28, Guy K. Kloss <guy.kloss@xxxxxxxxx> wrote:

> The installer offers a choice of SQLite (default) and MySQL. At what
> point is it advisable to use MySQL? In what situations will the
> capability of SQLite be not sufficient anymore?
>
> Guy
>
> --
> Guy K. Kloss
> School of Computing + Mathematical Sciences
> Auckland University of Technology
> Private Bag 92006, Auckland 1142
> phone: +64 9 921 9999 ext. 5032
> eMail: Guy.Kloss@xxxxxxxxx
>
> --
> Mailing list: https://launchpad.net/~sloecode-dev
> Post to     : sloecode-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~sloecode-dev
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Thomi Richards