4 Replies Latest reply on Oct 19, 2010 12:39 PM by rhauch

Modeshape and Firebird datasource

maxusoltsev Oct 15, 2010 7:39 AM

Hi all !

I tried to use firebird database for modeshape jpa source and found 2 issues:

1. i think, VALUE is reserved word in firebird (2.1), so hibernate can't map entity org.modeshape.connector.store.jpa.util.StoreOptionEntity

2. JpaStore sets hibernate.dialect only when jdbc datasource configured for store, and when i tried to use jndi datasource, i've got an error "dialect must be specified".

How can i solve this problems ?

1. Re: Modeshape and Firebird datasource

rhauch Oct 18, 2010 11:16 AM (in response to maxusoltsev)

Oh, that's unfortunate. Perhaps the easiest way to change the mapping is to override them with XML, as outlined in the Hibernate documentation [1]. I haven't done this and don't have an example. (When I get back from vacation, I will look into this.)

Has anyone else done this?

[1] http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/xml-overriding.html
Actions
2. Re: Modeshape and Firebird datasource

maxusoltsev Oct 19, 2010 1:34 AM (in response to rhauch)

Thank you, I'll try to override mappings. The first issue is not so important becouse I have just discovered that firebird reserved words list is reduced in last release (2.5, sorry, i can't test it now )
But the second problem (JpaStore sets hibernate.dialect only when jdbc datasource (not jndi) configured for store) is more important, imho.
Actions
3. Re: Modeshape and Firebird datasource

rhauch Oct 19, 2010 10:17 AM (in response to maxusoltsev)

I've created MODE-962 to track the Hibernate dialect issue. Should be fixed today in trunk and thus in 2.3 that should hopefully go out the door today.
Actions
4. Re: Modeshape and Firebird datasource

rhauch Oct 19, 2010 12:39 PM (in response to rhauch)

The fix for the Hibernate dialect issue (MODE-692) has been marked as resolved, and will be included in the 2.3 release.
Actions

Go to original post