Patch to store user info in different DB engines

[Chris Weyl]

On 10/28/05, Jeff Sheltren <sheltren at cs.ucsb.edu> wrote:
> No it doesn't.  The idea was that all database information should be
> stored in the same location.  Off the top of my head, I think that
> using separate database types would complicate DBManager.py quite a
> bit.  Currently it just assumes that everything is in the same DB, so
> there would need to be extra checks to see which DB holds which
> information, and then use the appropriate DB for each case.  In fact,
> this would probably mean using two DBManager objects, one for jobs
> and one for users (currently only one DBManager object is used by
> plague-server).  I don't know if that is a bad or good thing, I just
> think it is pretty complicated compared to the current situation.

Sounds... messy.  Hm.

> I think the easier thing to do is to write a tool for extracting all
> user info from sqlite in order to import it into mysql/pgsql.  I'll
> try to work on that this weekend.

Gotcha.  I think you're right...  just trying to keep the future 0.4
-> 0.5 migration pain at a lower level than 0.3 -> 0.4.  :)

                       -Chris