Considering glom but one major hurdle - I don't really want postgresql



Hello,

Glom seems like the almost perfect solution to several little database
jobs I have but there's one fly in the ointment - postgresql.

I've absolutely nothing against postgresql, I have some postgresql
databases, but most of the places that I want to use something like glom
I want to share the database with other applications (in particular with
DokuWiki) and the DokuWiki plugin I'm using uses sqlite3 by default and
mysql if you try hard.  :-)

I know glom limits the database usage to simple layouts but that's fine,
the DokuWiki plugin I use doesn't do anything at all fancy with the
database either.

I'm quite prepared to dig into the code myself and add the ability to
use other databases.  However I don't want to spend vast amounts of time
on this.  How standard/modular is the database access code and what
language is it written in?  I'm assuming it's written in C/C++ which is
OK by me as I've programmed in C since the 1980's (my job).

-- 
Chris Green



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]