Oops. Let's see if I can properly reply to the list this time: The Postgres support isn't in CVS yet, but there's a couple different patches for it. I started working on it and put my patches on the SBM at http://bugz.mostly-harmless.ca/show_bug.cgi?id=78, then right after someone else filed another bug saying they had gotten it working and put his patches at http://www.interlude.eu.org/~ad/pgscoop/ (he seems to be further along than me, but I havn't played with his patches.) Take your pick as to which one you'd rather play with. Also, which converter did you use that "worked nicely"? I tried about 3-4 of them when I was trying to get things working, and every single one of them had at least a couple of little problems with the scoop database. On Jun 22, 2004, at 1:16 AM, Jonathan Walther wrote: > Congratulations on the release of 1.0. I notice that "some Postgres > support was already committed". Is that in 1.0, or in the unstable cvs > branch? > > I'm willing to help out; I need a scoop site, and have been holding out > for Postgres for a while now. > > Who is doing the postgres support, and how far along are you? > > The automated MySQL->Postgres converter I ran on the Scoop database > worked nicely, even handling indexing, sequences, and dates. Then I > ran > out of time trying to track down where to specify Postgres as the DBI > module, and also ran out of time trying to find spots that depend on > the > format that the dates are stored in. > > Jonathan > > -- > Eukleia: Jonathan Walther > Address: 12706 99 Ave, Surrey, BC V3V2P8 (Canada) > Contact: 604-582-9308 (between 7am and 10pm, PST) > Website: http://reactor-core.org