Allow using a DB other than SQLite

[ianmcorvidae]

Not that SQLite isn't fantastic, but some of us already have PostgreSQL or MySQL installed on our systems (e.g., those of us who run musicbrainz-server already!) and plus, your database backend should be all nice and abstracted anyway.

[kepstin]

It should be, eh? At the moment, it's not very well abstracted, and I was planning to make use of some sqlite-integrated features like the integrated full-text search support. If I was going to support this, better sooner than later, though.

[kepstin]

I'm going to work on switching the database backend to be abstracted through libgda, which should allow using mysql/postgres databases.

[kepstin]

Hmm, libgda has this awesome new data object API that I want to use:
http://git.gnome.org/browse/libgda/tree/samples/vala/SampleDataObject.vala

But they haven't released a version with it yet :/ Should be in libgda-5.2 when that gets released. In the meantime I guess you'll have to build libgda from git if you want to build riker :/

[ianmcorvidae]

If you want to build riker, I assume you mean ;)

[kepstin]

So it looks like the way that I'm going to handle this is by Riker using a libgda 'DSN' for configuration. If it's not pre-existing, Riker will create a DSN using some internal default settings - .local/share/riker directory and SQLite engine.

However, a user can use the libgda configuration tools to point the DSN for riker at a different location - say, a PostgreSQL database they have laying about, and Riker will then use that instead.

The idea is to have good zero-configuration defaults, but that advanced users can do neat things.