cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <>
Subject [jira] [Created] (CAY-1772) Real support for DbEntity catalogs
Date Thu, 15 Nov 2012 08:56:13 GMT
Andrus Adamchik created CAY-1772:

             Summary: Real support for DbEntity catalogs
                 Key: CAY-1772
             Project: Cayenne
          Issue Type: Improvement
          Components: Core Library, Modeler
            Reporter: Andrus Adamchik
            Assignee: Andrus Adamchik
             Fix For: 3.2M1

While DbEntity has a 'catalog' property, we sort of ignore its presence, don't include catalogs
in generated SQL, and advise users to enter it in the "schema" field. However there is a practical
aspect of catalogs vs. schemas that became obvious when I started using 'cdbimport' with MySQL
(see CAY-1759). MySQL only has a single notion of "database" as a table namespace unit within
a given server instance. This maps to "catalog" in the MySQL JDBC driver (see [1], and [2]
for explanation of schemas vs catalogs across DBs). 

While using schema in place of catalog was fine with manual mapping, it became a problem with
reverse-engineered DataMaps that left the schema empty. So all the generated SQL based on
such DataMaps would use bare table names, and if the catalog is not a part of JDBC URL, a
namespace conflict would occur.

So we need to :

1. honor catalog setting in generated SQL
2. add "default catalog" DataMap, and "catalog" to DbEntity fields in the Modeler
3. add catalog selection to reverse engineering dialog in the Modeler


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message