I'm guessing this was done for the sake of MySQL compatibility: http://stackoverflow.com/a/1142588
Shouldn't this behavior only be on in MySQL compatibility mode? Gili On Wednesday, February 5, 2014 5:14:09 PM UTC-5, Gili wrote: > > Hi, > > I have the following table definition: > > CREATE TABLE table_type (id TINYINT NOT NULL AUTO_INCREMENT(0), name > VARCHAR(30) NOT NULL); > INSERT INTO table_type SET name = 'A'; > INSERT INTO table_type SET name = 'B'; > INSERT INTO table_type SET name = 'C'; > etc... > > I'd like to map the "id" to an enum's ordinal() value (which is > zero-based). When I upgraded from version 1.3.174 to 1.3.175 I started > getting this error: > > CREATE TABLE table_type (id TINYINT NOT NULL AUTO_INCREMENT(0), name > VARCHAR(30) NOT NULL): Unable to create or alter sequence > "SYSTEM_SEQUENCE_92282573_A9B5_4684_8F33_3D00A93F02E7" because of invalid > attributes (start value "0", min value "1", max value > "9223372036854775807", increment "1"); SQL statement: > CREATE TABLE table_type (id TINYINT NOT NULL AUTO_INCREMENT(0), name > VARCHAR(30) NOT NULL) [90009-175] > > Why is a value of 0 disallowed? > > Thanks, > Gili > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
