Are their any negative effects in using the Oracle SQL Mode?

[Former Member]

Are their any negative effects in using the Oracle SQL Mode? We would like to use this mode for the coalesce function, but want to understand if this will have any negative impacts.

[lbreddemann · Accepted solution]

Hi Chris,

what coalesce function you mean?

The mySQL DB has one, Oracle has (as PL/SQL function) one but MaxDB does provide such sql function.

Perhabs you want to use the VALUE() function for that ?

<a href="http://dev.mysql.com/doc/maxdb/en/cf/633171c03511d2a97100a0c9449261/content.htm">MaxDB Docu</a>

If you refer to the ALTER INDEX ... COALESCE command on oracle: that one neither makes sense in MaxDB nor is it available.

Concerning performance or stability there is no drawback in using the ORACLE mode.

SAP Netweaver acually uses it (or better it uses a copy of that mode).

KR Lars

[Former Member · Accepted solution]

I have existing queries that use the coalesce function, similar to mySQL. T

hanks for the answer, I wanted to make sure that there was no negative impacts.

[alexander_schroeder]

Hello Chris,

in Oracle mode there are indeed some differences e.g. regarding type names, reserved words. You may want to use the VALUE function which is available in INTERNAL mode, if possible.