Hide Forgot
Workaround: Workaround Exists project_key: SOA I'm going through the supported set of databases trying to execute the modeshape ddl scripts with the native database administrative utilities. I'm looking at DB2 right now and wondering why '%' was chosen as statement delimiter. `db2 -vf create.modeshape-jpa-connector.ddl` results in errors like: create table MODE_SIMPLE_LARGE_VALUES (SHA1 varchar(40) not null, COMPRESSED smallint, DATA blob(255) not null, LENGTH bigint not null, TYPE varchar(255) not nu%l, primary key (SHA1)) DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0104N An unexpected token "%" was found following "primary key (SHA1)) ". Expected tokens may include: "END-OF-STATEMENT". SQLSTATE=42601 One can workaround this by adding the -td% option but why not use ';' as a delimiter given there is a -t option that. Or even why not use simply new line as a separator given db2 utility uses that by default? I mean it makes most sense to use the default delimiter or ';' because of its wide use. I'll update this issue if I see other glitches. IMHO the \r before statement delimiter should be removed. In the case of mssql and sybase I have yet to check how it works though.
the create table script above is strange. I'm looking at the created script from SOA: create table MODE_SIMPLE_LARGE_VALUES (SHA1 varchar(40) not null, COMPRESSED smallint, DATA blob(255) not null, LENGTH bigint not null, TYPE varchar(255) not null, primary key (SHA1)) and it has "null" where "nu%l% is.
but we can go ahead and change all delimiters to ";"
I didn't quiet understand your first comment but please let me check mssql and sybase tomorrow. I'm almost sure mssql takes ';' but not so about sybase.
btw IIRC MS SQL server is using "go" as commit transaction but given we shouldn't really need these statement in separate transactions, ';' should be working fine there
While we're at renaming directories, lets rename MySQL5InnoDB to MySQL.
Why not.. hopefully there are not too many people running *the last good MySQL version* - 3.x :)
Link: Added: This issue is a dependency of MODE-1022
Here are the new version of the scripts creates from a soa build. Unzip / replace the schema's directory under modeshape.
Attachment: Added: schemas.zip
The changes have been checked into ModeShape and into the soa build to handle producing ddl scripts with the requested delimiter and handle Sybase.
I see one issue with sybase - between statements I see \rGO\n instead of \nGO\n Thanks!
Everything looks fine to me now. We do not ship sybase DDL any more.