Re: AW: AW: NO FIXED LENGTH COLUMN, still valid?

[John L. Singleton]

Elke,
I upgraded to 7.5.00.15 and now NO FIXED LENGTH COLUMN is recognized at 
the SQL prompt. However, when I was investigating the part about only 
the first n-1 primary keys being exempt from NO FIXED LENGTH COLUMN, I 
came across this:

sqlcli test=> create table nflc_test3 (ID char(5)) NO FIXED LENGTH COLUMN
0 rows affected (367 msec)
sqlcli test=> insert into nflc_test3 values ('12345')
1 row affected (9 msec)
sqlcli test=> insert into nflc_test3 values ('123456')
* -8004: Constant must be compatible with column type and length 
SQLSTATE: 22001
sqlcli test=>

As you can see from the above output, NO FIXED LENGTH COLUMN is accepted 
as valid syntax, but it does not appear to be enforced. Any thoughts?

Thanks again,
JLS
Zabach, Elke wrote:
John L. Singleton wrote
 

Hi Elke,
I get the same result in sqlcli and SQL Studio. This output, however, is
from SQL Studio.
Kernel Version: 7.5.05
   

Aaah, here we are. You are using 7.5.00.05, but this feature was implemented with 
7.5.00.11. With your version it can't do. Please upgrade to a newer one.
Elke
SAP Labs Berlin
 

Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed
Syntax error or access violation;-3014 POS(46) Invalid end of SQL
statement.
create table nflc_test (foo int PRIMARY KEY) NO FIXED LENGTH COLUMN
To save you time, the POS(46) points to "NO."
Thanks,
JLS
Zabach, Elke wrote:
   

John L. Singleton wrote:
     

Hello all,
Does MaxDB still support the NO FIXED LENGTH COLUMN clause? I've tried
several variations of this statement, but with no luck.
For example:
create table nflc_test (foo int PRIMARY KEY) NO FIXED LENGTH COLUMN
-3014: Invalid end of SQL statement SQLSTATE: 42000
I'm sure it's something really simple that I'm missing. Any ideas?

       

No idea, too, as it works fine for me.
Which kernel-version are you using?
Which tool are you using?
Which sqlmode are you using?
Which errorposition is given (position in the statement where the error
     

was found)? Maybe a funny char is behind the correct statement? (We had
this here in private scripts, just an idea)
   

Elke
SAP Labs Berlin

     

Cheers,
JLS
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
       

http://lists.mysql.com/[EMAIL PROTECTED]
   

       

 

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]