Mappingtool generates bad DDL for sybase (J2ee tutorial)

Question

Running the mappingtool on the J2EE tutorial app (3.0.0RC1) generates bad
DDL for sybase. It's trying to create a table with a column of type
"IndexName":
C:\devtools\kodo\samples\j2ee>mappingtool -a refresh package.jdo
0 INFO [main] kodo.Tool - Mapping tool running on type "class
samples.j2ee.Car" with action "refresh".
0 INFO [main] kodo.Tool - The tool is now reading existing schema
information; this process may take some time. En
able the kodo.jdbc.Schema logging category to see messages about schema
data. Also see the -readSchema tool flag.
3716 INFO [main] kodo.Tool - Recording mapping and schema changes.
Exception in thread "main" kodo.util.FatalException:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length
or scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:431)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
NestedThrowablesStackTrace:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at
com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:67)
at
com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnectionDecorator.java:19)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConne
ctionDecorator.java:506)
at
com.solarmetric.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:125)
at kodo.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1042)
at kodo.jdbc.schema.SchemaTool.createTable(SchemaTool.java:803)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:334)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:186)
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:364)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
Anyone else seen this? It works ok with Hypersonic (though i can't get the
tutorial app to run with hypersonic - see my earlier post).
Alex.

Answer 1

Some bugs in RCs sometimes don't make it into Bugzilla as it is a
release candidate and not production quality.
I would reocmmend upgrading as it fixes a number of major bug fixes and
you should be able to use the same eval key.
Alex Robbins wrote:
Abe White wrote:
I should also have asked: what JDBC driver are you using?Hi Abe,
I haven't tried with RC2 - has this been fixed in RC2? I didn't find this
bug on bugzilla.
I'm using Sybase JConnect JDBC driver (com.sybase.jdbc2.jdbc.SybDriver in
jconn2.jar) - looks like this is the version:
jConnect (TM) for JDBC(TM)/5.5(Build 25008)/P/JDK12/Tue May 29 14:37:46
2001
Should I upgrade from RC1 to RC2, and if so, can I continue to use the
same eval license key or can i download a new one?
thanks,
alex
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com