Re: default next value for SEQ

We support the SQL Standard syntax below :

bar integer generated by default as identity primary key

The standard does not allow "next value for" a named sequence in the default 
clause, which is limited to constants and simple functions such as 
CURRENT_USER and CURRENT_TIMESTAMP.

Fred


----- Original Message ----- 
From: "Dimitri Maziuk" <dmaziuk@xxxxxxxxxxxxx>
To: <hsqldb-user@xxxxxxxxxxxxxxxxxxxxx>
Sent: 03 April 2007 20:18
Subject: [Hsqldb-user] default next value for SEQ



Any plans to add support for this:
 create table foo (
   bar integer default next value for barsequence primary key
 )

java.sql.SQLException: Wrong data type or data too long in DEFAULT clause:
NEXT in statement [ CREATE TABLE FOO ( BAR INTEGER DEFAULT NEXT]
        at org.hsqldb.jdbc.jdbcUtil.sqlException(Unknown Source)
        at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
        at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)

Dima


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Hsqldb-user mailing list
Hsqldb-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/hsqldb-user 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV