[
https://issues.apache.org/jira/browse/OPENJPA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466803
]
Marc Prud'hommeaux commented on OPENJPA-106:
--------------------------------------------
We may not be reading the database prefix correctly. Can you enable trace-level
logging (by setting "openjpa.Log" to "DefaultLevel=TRACE"), and send us the
logging output from the mappingtool run? That should show all of the JDBC calls
we are making to inspect the database metadata.
> MappingTool does not function properly when using database-prefix in
> table-names on mysql
> -----------------------------------------------------------------------------------------
>
> Key: OPENJPA-106
> URL: https://issues.apache.org/jira/browse/OPENJPA-106
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Environment: OS: Windows and Unix, openjpa-0.9.6-incubating,
> mysql-5.x, mysql-jdbc-connector 3.?? and 5.0.4
> Reporter: Markus Herzog
> Priority: Minor
>
> Hi,
> the problem i'm going to describe here probably only exists when using
> openjpa together with mysql. Maybe this is even a bug in the
> mysql-jdbc-connector.
> The MappingTool (and MappingToolTask) does not notice that a table exists
> when the name of the table also contains the name of the database (for
> example <class name="my.company.MyClass" table="my_database.MYCLASS" />)
> Everything else is working satisfyingly with this prefix-thingy. As a work
> around i'm removing the prefixes from my metadata before using mappingtool
> and put it back in afterwards. (I need this prefix after all because i'm
> using multiple databases at once).
> Maybe when the mappingtool asks the database for the table
> "my_database.MYCLASS", the jdbc-connector tells openjpa that no such table
> exists. If so, can't mappingtool ask the database differently?
> Thank you for listening and keep up the good work,
> Markus
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
