openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Herzog (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-106) MappingTool does not function properly when using database-prefix in table-names on mysql
Date Tue, 23 Jan 2007 15:21:49 GMT
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.


Mime
View raw message