× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



FWiW: The SQL parser does not care about "white space" [or lack of] in that, nor many other cases. Extraneous blanks are overlooked during parsing, anywhere I can think of, before or after either a closing or opening parenthesis. Each of the following should always pass without syntax errors [using SQL naming]; that two statements are SELECT versus CREATE, is immaterial for the purpose of making the point:

create table QTEMP . FOO( T DECIMAL (1)default 7 )

select DECIMAL ( 1 / 3 , 6 , 6 )from SYSIBM . SYSDUMMY1

select RAND ( ) from SYSIBM . SYSDUMMY1

Regards, Chuck

On 15 Aug 2012 11:38, rob@xxxxxxxxx wrote:
I bet that it doesn't like the space between decimal and the
parenthesis. The ( is pos 31. <<SNIP>>

On 15 Aug 2012 08:50, James Lampert wrote:
<<SNIP>>
334 create table SM_Addresses
335 (
336 address_id NUMERIC(20),
337 type INTEGER,
...
> 345 logtitude Decimal (%10,%7),
...
SQL0104 30 345 Position 31 Token ( was not valid.
Valid tokens: AS NO FOR NOT FILE WITH CCSID CHECK LOGGED UNIQUE
COMPACT DEFAULT.
<<SNIP>>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.