Hi, On Wed, 19 Feb 2003, Daniel Rahn wrote:
I would vote for a third options: Stay away from commands / options that are marked as a addon special to this database. SQL92 does not define very much, but the common base runs on all databases.
The problem for special syntax should only arise when you create the database and the initial tables, which might need special keywords that are different in every database. This can be handled with different create scripts and should be no problem.
The system operation however should be based on a common standard, which SQL92 is. Every database on the market today supports SQL92.
I second this. You cannot optimize your statements for a special database then. But the question is, what is wanted? If you force OTRS to use one special database you could optimize all statements and your application for that. If this is the case I will stop to try to get it running with SAPDB. So what do you think? CU, Wolfgang