-------------- Original message ---------------------- From: Paul McNett <[EMAIL PROTECTED]> > Gary Thompson wrote: > > Chris, > > I hope you have success in completing a migration to GNU / > > Linux based systems. > >> Is there any reason to choose one database engine rather than > >> another? It's only a single user application, no complex locking > >> requirements. I've got both mySql and postgresql databases already > >> on my system. > >> > > If you're looking for an engine "similar" to access (in terms of light > > weight), I prefer SQLite. The reason is that It's a very simple engine, > > is file based (that's probably the only similarity) and you don't really > > need to administer a database server (MySQL and PostgreSQL are > > examples). However, if the databases are there and available already > > then there's no reason not to use them. Another PRO in the SQLite > > direction is that it's probably quite easy to migrate between different > > machines since a file copy will do the job, as opposed to an export / > > import operation for an SQL Server. > > I second the recommendation for sqlite. Much simpler. However, it is > functionally single-user and for large datasets a dedicated server will > be better.
One caveat about SQLite. It is has become popular as an embedded database. Ubuntu for one uses it to store information. The problem arises if you try to load a newer version of SQLite in a system where it is already installed. Uninstalling the old version is not always possible because of dependency issues. You can run versions side by side but you need to plan this carefully as it is possible to compile against the wrong libraries when building the new binary. That being said I use it as a light weight datastore. > > For my app, which gets distributed to my customer's clients, the basic > install is single-user sqlite. They can pay more for the multi-user > MySQL version, though. > > The choice of database backend doesn't need to happen right now. Start > with the one that makes sense, and know that you can migrate to another > one later if needed, without having to change much of your Dabo code at all. > > Paul > > > -- Adrian Klaver [EMAIL PROTECTED] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
