Moving udd away from sqlite

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

...
> Some routes are: - move to postgresql using the lower level APIs
> and add storm later - work on the storm patchset to make it
> reliable with sqlite - do both postgresql and sqlite at the same
> time.
> 
> My recommendation, given the existing investment, is to bite the 
> bullet: bring up a postgresql instance in staging and prod, dump
> and import the data to it, and switch over to postgresql. Debug any
> issues in real-time, and move on. The depth of potential issues is
> sharply limited, because postgresql handles many more combinations
> of client interaction than SQLite (by design and necessity).
> 
> -Rob
> 

Note that there is no staging for udd, and we currently do not even
have backups of the databases.

I'm personally most in favor of an incremental approach that brings in
storm (with a hack for the isolation level), and then postgres.

I know that we are all in agreement that moving to postgres is what we
want to do. The argument is mostly about how we do the transition, and
what steps are most relevent towards getting there.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/gZccACgkQJdeBCYSNAAPnXQCggMrjji6a9zv5yRaJHTsr9XSO
PzMAmQF6bZs3InNX/Mc522eEgloV+lmt
=PvE3
-----END PGP SIGNATURE-----