It is my jagged trollish hook :-) What good is Postgres for scoop? Honestly nothing. I moved to Postgres for a bunch of features that MySQL didn't have (triggers, transactions, FK's, etc...). YMMV. The important part of my post is that the default schema needs some indexing. Last I checked, MySQL should support indexes, even unique ones, quite well. -- Cory R. King William Scott Lockwood III wrote: > On Sat, 2006-07-15 at 18:28 -0700, Cory R. King wrote: >> If anybody is considering Postgres (and you should be) > > Ok, I'll bite. :-) Now, admittedly, I'm very biased (I have had many > good conversations with Brian Aker (who is MySQL's chief architect right > now) about MySQL, and I like it better) but why should we be thinking > about PostgreSQL? I've looked at it - There is even a good vendor who > will provide commercial support for it - but what does it give me? If > you find often that you have these corner cases that MySQL doesn't > handle well, then maybe you need to go through the severe pain of going > from one to the other. What does Scoop do that MySQL doesn't handle > well? > > Regards, > Scott >