-
1. Re: Issues with ddl export and mysql
bcarothers Apr 13, 2010 5:15 PM (in response to meetoblivion)What Hibernate dialect are you using?
-
2. Re: Issues with ddl export and mysql
meetoblivion Apr 13, 2010 7:49 PM (in response to bcarothers)tried it both with none specified (let hibernate choose one) and then explicitly org.hibernate.dialect.MySQL5Dialect
-
3. Re: Issues with ddl export and mysql
bcarothers Apr 14, 2010 7:16 PM (in response to meetoblivion)I think something else is afoot. Could you please jump on IRC and pastebin your config? I can take a look at it tonight. Thanks!
-
4. Re: Issues with ddl export and mysql
meetoblivion Apr 14, 2010 8:55 PM (in response to bcarothers)here's the pastebin link
and for those who don't want to travel
- Here's one w/ nothing specified
- <mode:source jcr:name="LiveSource"
- mode:classname="org.modeshape.connector.store.jpa.JpaSource"
- mode:rootNodeUuid="abcdefghjiukr"
- mode:autoGenerateSchema="update"
- mode:dataSourceJndiName="jdbc/JCRADMIN"
- mode:nameOfDefaultWorkspace="liveWorkspace"/>
- Here's an InnoDB example
- <mode:source jcr:name="LiveSource"
- mode:classname="org.modeshape.connector.store.jpa.JpaSource"
- mode:rootNodeUuid="abcdefghjiukr"
- mode:autoGenerateSchema="update"
- mode:dialect="org.hibernate.dialect.MySQL5InnoDBDialect"
- mode:dataSourceJndiName="jdbc/JCRADMIN"
- mode:nameOfDefaultWorkspace="liveWorkspace"/>
- and normal
- <mode:source jcr:name="LiveSource"
- mode:classname="org.modeshape.connector.store.jpa.JpaSource"
- mode:rootNodeUuid="abcdefghjiukr"
- mode:autoGenerateSchema="update"
- mode:dialect="org.hibernate.dialect.MySQL5Dialect"
- mode:dataSourceJndiName="jdbc/JCRADMIN"
- mode:nameOfDefaultWorkspace="liveWorkspace"/>
I'm in IRC now. also note, these don't all live in the file at once, but are examples...
-
5. Re: Issues with ddl export and mysql
bcarothers Apr 14, 2010 10:06 PM (in response to meetoblivion)If you could, please update from trunk and then run the DDL generator with -model Simple and -dialect MySQL5InnoDB. This will (theoretically) generate the same DDL that Hibernate would generate when you set autogenerateSchema = create. I'd like to hear if you still get the same LOB malfeasance when the DDL is created that way.
Thanks for working through this with me!
-
6. Re: Issues with ddl export and mysql
meetoblivion Apr 15, 2010 8:35 AM (in response to bcarothers)yeah - it still doesn't work for create/update. It's a bit concerning since I'm the one who sent you guys the code for enabling configurable hibernate options in this case.
-
7. Re: Issues with ddl export and mysql
meetoblivion Apr 17, 2010 7:47 AM (in response to meetoblivion)Brian, issue ended up being a bit more complicated than thought.
I opened https://jira.jboss.org/jira/browse/MODE-723 as a result. Even though we got around the BLOB type issue, MySQL doesn't like having a name w/ 512 length PK. Max is 500 in MyISAM and ~330 something in InnoDB
-
8. Re: Issues with ddl export and mysql
bcarothers Apr 17, 2010 6:19 PM (in response to meetoblivion)Well, our longest value in that column currently is 32 characters long, so I think we can live with cutting that column down a bit. I'll have a patch submitted as soon as the regression test passes.
Out of curiosity, what's the 2-byte charset that you're using? Also, are you still seeing the wonky DDL when autogenerateSchema is create or update?
Thanks for your patience as we work through this.