SQL requiring blanks (was: it did the job)

["Peter Colpaert" <Peter.Colpaert@xxxxxxxxxxxx>]

Hi gang,

I found out why our SQL requires a blank after the commas when using the
substr()  and other functions:

If your decimal separator is *comma (as is the case on our systems), you
need a blank after each comma, to indicate that you are entering the next
parameter, and not a number with decimals.

I just knew it had to be something simple (but well hidden).

Note to IBM'ers monitoring this list:  Is it possible to have a new version
of SQL where you can specify your own separator character, so that we could
use for instance substr(field:1:1)?

Regards,

Peter Colpaert
Application Developer

Honda Europe NV
Langerbruggestraat 104
B-9000 GENT
Peter.Colpaert@honda-eu.com
Tel: +32 9 2501 334
Fax: +32 9 2501 231
----------
Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
----------



______________________________________________________________________
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
the entity to whom it is addressed and others authorised to receive it. If
you have received it by mistake, please let the sender know by e-mail reply
and delete it from your system.
If you are not the intended recipient you are hereby notified that any
disclosure, copying, distribution or taking any action in reliance of the
contents of this information is strictly prohibited and may be unlawful.
Honda Europe NV is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.