On Tue, May 27, 2008 at 9:08 AM, Chris G <[EMAIL PROTECTED]> wrote: > On Wed, May 28, 2008 at 12:47:35AM +1000, 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. >> > Yes, I had wondered about using SQLite, it sounds as if it will make > things simple. If I'm careful and keep things modular it shouldn't be > too difficult to move to MySQL or PostgreSQL anyway should it?
The major issue that I have with in SQLite is the lack of support for different data types. Dabo solves this somewhat by doing a O/R type mapping for you. Other than that, it is a nice alternative if you are doing an app that will be widely deployed through an installer to people that just want it to work and don't have the knowledge to set up a more traditional database. As Uwe mentioned though, it can't be used in multi-user/multi-application environments. _______________________________________________ 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]
