[jboss-jira] [JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query

[John Ament (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144754#comment-13144754 ] 

John Ament commented on WFLY-5919:
----------------------------------

[~smarlow] yes, its not an issue of strings (we actually use constants here).  I apologize, as I also created an issue in HHH for this with more info.  The fact that switching from schema to catalog fixes it 

The HHH issue is https://hibernate.atlassian.net/browse/HHH-10408 which was closed - rejected.  While I can update my mappings to use catalog over schema, it doesn't seem consistent with prior versions of hibernate (in fact, my output shows this was working fine in 5.0.1).  In addition, this may be an issue for your customers upgrading to EAP7.

> Wildfly 10 CR5 Regression - Schema not added to query
> -----------------------------------------------------
>
>                 Key: WFLY-5919
>                 URL: https://issues.jboss.org/browse/WFLY-5919
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 10.0.0.CR5
>            Reporter: John Ament
>            Assignee: Scott Marlow
>
> My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
> {code}
> 2016-01-03 08:30:43,626 WARN  [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
> 2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
> 2016-01-03 08:30:43,627 INFO  [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
> {code}
> I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
> The config looks like this
> {code}
> @Table(name = "types", schema = "config")
> {code}
> I have an orm.xml file, I tried removing the default schema stanza without luck.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)