What’s the hibernate dialect for Teradata 17 in Hibernate 6+ ?
The one I have used causing me the below error:
‘unable to resolve name org.hibernate.dialect.TeradataDialect dialect as strategy org.hibernate.dialect.dialect’ . I have also used Teradata14Dialect but no luck on that.
Any suggestions please.
With Hibernate 6 Teradata’s dialect was moved to the new hibernate-community-dialects artifact.
Find out more in our migration guide.
getting the below error;
strategyselectionException: Unable to resolve name [org.hibernate.community.dialect.TeradataDialect] as strategy [org.hibernate.dialect.Dialect]
Did you add a dependency for the hibernate-community-dialects artifact?
Yes, now getting this error:
StrategySelectionException: could not instantiate named strategy class [org.hibernate.community.dialect.TeradataDialect]
I am setting it from config class into a Hashmap like below:
someObject.put(“hibernate.dialect”, “org.hibernate.community.dialect.TeradataDialect”);
entityManagerFactoryBeanOBject.setJpaPropertyMap(someObject);
That should work though, what is the full exception stack trace?
org.hibernate.boot.registry.selector.spi.StrategySelectionException: could not instantiate named strategy class [org.hibernate.community.dialect.TeradataDialect]
An exception has something called a stack trace where you see the error originates from, as well as a possible exception cause. Without that information, nobody can help you.
full stack trace cannot be shared as it’s from restricted system.
but I am using teradata 17.10 with spring boot 3, java 17, hibernate 6.
Also, below the stack trace I see this:
Well, then give your user permission to query the restricted words.
Is there any way to bypass the getSqlKeywords() function of hibernate ?
I didn’t find much about any property or anything though.
You can create a custom subclass and override the registerKeywords method to do nothing, but you might run into other issues then.
Yes, I agree with that.
I am using teradata 17.10 with spring boot 3, java 17, hibernate 6.