Yeah, but Ikonboard sounds like a small, one or two man project, so, I can kinda understand some things taking some time.
I know phpBB had issues with pgsql when the latest version came out.
I've found that if you code your stuff on a "real" db, (i.e. firebird, sybase, oracle, postgresql, mysql) that converting it to another database is easier than if you start on mysql. It seems MySQL teaches people bad habits, like the '' being used for an int.
Admittedly, some MySQLisms make conversion to MySQL painful, like timestamp columns (the first one in a table definition) being an auto-updating field in myisam (don't know about innodb, but I don't think so) when the SQL spec clearly defines it as just being a timestamp type that isn't autoupdating. That bites lots of folks.
Oddly, if people developed these kinds of things for innodb tables some of this would go away, like the lack of foreign keys. Heck, innodb supports on delete cascade, on update cascade foreign keys. But of course, in typical MySQL fashion, you have to put foreign key definitions at the end of your item list,,, ugh. If you put your fk defitions in the field portion of the item list (i.e. id int references master(mid))... will just be ignored with no warning.
