Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 59824 invoked from network); 23 Jan 2007 19:13:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2007 19:13:14 -0000 Received: (qmail 96616 invoked by uid 500); 23 Jan 2007 19:13:17 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 96520 invoked by uid 500); 23 Jan 2007 19:13:17 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 96417 invoked by uid 99); 23 Jan 2007 19:13:16 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2007 11:13:16 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2007 11:13:09 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 864F77142D7 for ; Tue, 23 Jan 2007 11:12:49 -0800 (PST) Message-ID: <9173532.1169579569544.JavaMail.jira@brutus> Date: Tue, 23 Jan 2007 11:12:49 -0800 (PST) From: "Marc Prud'hommeaux (JIRA)" To: open-jpa-dev@incubator.apache.org Subject: [jira] Commented: (OPENJPA-106) MappingTool does not function properly when using database-prefix in table-names on mysql In-Reply-To: <13345542.1169565709066.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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 ) > 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.