Considering a project which will target DB2 UDB on Linux as the primary / suggested platform, but also support MySQL and/or PostgreSQL as our project is GPL so it would be "slightly" rude then to
require a licensed database to even "kick the tires"... but then DB2 does rock!
Anyway, considering that focus, the database class we develop will handle making the correct connection based on the RDBMS configuration. For DB2 it will connect via CLI (from C++ and PHP) and use
appropriate interfaces to the other RDBMS's we support. This class will need to modify the SQL based on the back end, and that is my specific interest with this post. DB2 could be doing fancy stored
procedures for us, but that means more drastic SQL customizations between RDBMS's. If we try to stick to SQL capabilities which the RDBMS's all support, then of the subtle differences which do exist
is there any suggested tools or documentation to aid in customizing the SQL for each RDBMS... or maybe like a matrix of the SQL language and check boxes for which RDBMS's support each aspect of the
language.
Basically open to suggestions for how others have handled making an application work with multiple RDBMS's and yet take advantage of enhanced features which might even be unique to one RDBMS.
Thanks!
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
Remove the upper case letters NOSPAM to contact me directly.