PostgreSQL work

[Derek Atkins]

Matthew Vanecek <mevanecek at yahoo.com> writes:

> Not yet.  It's not really to a point where I'd release it to the public
> for input (i.e., the basic functionality is still being rewritten--but
> I'm getting closer).  I've been unable to work on it in a while due to a
> back injury (for some reason, sitting was just very painful).  I'm
> trying to get back into it now, and pick up where I left off.  I know
> Derek is anxiously waiting results, and I'd like to get it further along
> myself. :)

Indeed.  In real-life I implemented an embedded-mysql data store for a
project and just got it working today..  So I know it works (although
not quite the way I expected it to originally).  But it's a proof of
concept for using a SQL system without requiring a standalone SQL
Server.

But yes, I am anxiously waiting on your results.  My hope is that
you've separated out the SQL generation from the actual Postgres
library, so that I could re-use all your SQL generation code but just
use the mysql API functions instead...  And hopefully I don't have to
copy-and-paste the SQL parts....

> Thanks for the offer, though.  I'll probably get a sourceforge cvs
> account or something eventually, until it's clean enough to put into the
> main Gnucash tree.  At that point, input will most definitely be sought
> after.  It is, after all, a rewrite, and not a cleanup.  Most of the
> stuff is original code.

I don't see why it can't go into the GnuCash CVS HEAD....  I see no
reason to build it externally.  I certainly wouldn't put it into the
1.8 branch, but that's what branches are for :)

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available