Author Topic: PostgreSQL as an alternative to MySQL? (Read 20184 times)

Alreadythere · « **Reply #15 on:** February 21, 2008, 07:27:35 pm »

Quote from: TigerDragon on February 21, 2008, 07:23:16 pm

Yep... pretty much what I was planning.

Ignore my comments then

Glarawyn · « **Reply #16 on:** February 28, 2008, 10:54:05 pm »

For supporting multiple databases, should we be looking at something like PDO, PEAR MDB2, or some abstraction layer?

Looks like PEAR MDB2 supports fbsql, ibase, mssql, mysql, mysqli, oci8, pgsql, querysim, and sqlite.

Alreadythere · « **Reply #17 on:** February 28, 2008, 11:30:59 pm »

Something like PDO may help - though that would require a complete rewrite of all DB access too.

Glarawyn · « **Reply #18 on:** February 29, 2008, 02:29:50 am »

Quote from: Alreadythere on February 28, 2008, 11:30:59 pm

Something like PDO may help - though that would require a complete rewrite of all DB access too.

PDO doesn't look like a complete solution...

Right now our SQL is written for MySQL and only MySQL. It might be generic enough for PGSQL or SQLite, or it may not be. I know in some of my modules I have queries that will only work in MySQL as I've specified the MySQL storage engine to use.

PEAR MDB2 does some sort of abstraction/translation so that the SQL queries will work on any database supported by PEAR MDB2...

I've heard a number of arguments on why PostgreSQL is superior to MySQL, and those arguments just don't apply for what we're doing with BeBot and MySQL. Referential integrity, foreign keys, full transaction logging, and what have you just aren't a concern for BeBot.

If we were to officially support a database other than MySQL my vote would be for SQLite first as it doesn't require running of a database server, thus lowering the requirements for running BeBot significantly. BeBot + SQLite would be something IGN users (poor souls) looking for an upgrade path would go for.

Blueeagle · « **Reply #19 on:** February 29, 2008, 02:39:04 am »

Quote from: Glarawyn on February 29, 2008, 02:29:50 am

BeBot + SQLite would be something IGN users (poor souls) looking for an upgrade path would go for.

Whistling into a modem would be an upgrade for IGN users. </joke>

Alreadythere · « **Reply #20 on:** February 29, 2008, 02:50:48 am »

Quote from: Glarawyn on February 29, 2008, 02:29:50 am

Right now our SQL is written for MySQL and only MySQL. It might be generic enough for PGSQL or SQLite, or it may not be. I know in some of my modules I have queries that will only work in MySQL as I've specified the MySQL storage engine to use.

I think some of the datatypes are pretty MySQL specific. Maybe even a couple of the MySQL queries I used, I haven't checked what is supported by which sql server.

Quote from: Glarawyn on February 29, 2008, 02:29:50 am

I've heard a number of arguments on why PostgreSQL is superior to MySQL, and those arguments just don't apply for what we're doing with BeBot and MySQL. Referential integrity, foreign keys, full transaction logging, and what have you just aren't a concern for BeBot.

I think all of that could be done with MySQL and InnoDB tables too. Not that we need it, true.

Quote from: Glarawyn on February 29, 2008, 02:29:50 am

If we were to officially support a database other than MySQL my vote would be for SQLite first as it doesn't require running of a database server, thus lowering the requirements for running BeBot significantly. BeBot + SQLite would be something IGN users (poor souls) looking for an upgrade path would go for.

Would be nice, but I think there would be datatype problems again.

And Blue, thats no joke

Hyde · « **Reply #21 on:** August 09, 2008, 04:16:07 am »

Just to throw in $.02 from the "I don't do DB work" side of the fence ... anything that would let SQLite work would be very welcome. I wouldn't use it for orgbots or raidbots, but I'd definitely use it for a personal bot. I travel alot and don't like to have to run XAMPP from a USB stick all the time (so I just don't bother). But if it was running SQLite and I could just run the one thing to have it I would definitely use it.

It may be -way- outside the usual scope of BeBot but it would sure be useful.