Re: ANSI SQL COMPATIBILITY

You need to separate SQL and Stored Modules (Orcale PL/SQL, MS Transact SQL) when dealing with standards, because with the later developing standard code is almost impossable. As more and more vedors (including MS) supply Java Stored Modules this problem will go away.

This is quite a large and complex area I would recommend reading :

SQL Reference 8.0 : Section 1-3 and Appendix A

to get more information on Oracle's compliance. Remember always use the FIPS flags to ensure you are writing Standard SQL.

Regards
David Russell

matta_at_metratech.com wrote in message <71su9l$3hv$1_at_nnrp1.dejanews.com>...
>Hello All
>
>Our system needs to be database vendor independent. We will be mainly
>talking to MS SQL Server, Oracle, Sybase and maybe IBM-DB/2. My questions
>are:
>
>1) Are all these vendors following one standard for SQL coding, ie. ANSI
 SQL.
>I think MS and Sybase have their version of SQL called Transact-SQL.
>
>2) What are the common pitfalls of ANSI SQL coding? I am sure it works
 well
>with native commands but might not work for little complicated stuff like
>datepart, etc... Our queries (as of now) are very simple and will probably
>work for all kinds of vendors. However, I do not want to rule out the idea
>of having some tricky joins as well as using in-built functions.
>
>3) Is there a FAQ on this or some research that somebody has already done
 on
>it?
>
>Please either respond to this post or mail me at matta_at_metratech.com,
>whichever is convenient.
>
>Thanks
>
>Raju Matta
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Thu Nov 05 1998 - 00:00:00 CST