Hi, On Wed, Feb 19, Wiktor Wodecki wrote:
The system operation however should be based on a common standard, which SQL92 is. Every database on the market today supports SQL92.
not a good idea, in my company there a "big plans" (grin) for OTRS and I don't want to send several SELECT just because if would also work on some curious other databases I'll never use :-)
And what might be the big features that you need and that would end in multiple SQL statements instead of one? Don't get me wrong. I just want to know what it is that you need. Joins etc. are defined in the standard and are no problem, subselects aren't either. What do you need exactly? greets, Daniel Rahn -- SuSE Linux AG | phone: +49 (0) 911 74053 0 Enterprise Support Services | fax: +49 (0) 911 74053 674 Deutschherrnstr. 15-19 | http://www.suse.de/en/support 90443 Nuernberg | GERMANY