You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2012/05/18 08:51:07 UTC
[jira] [Updated] (CAY-1152) DbEntity schema is ignored when
checking for DbEntity name uniqueness
[ https://issues.apache.org/jira/browse/CAY-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrus Adamchik updated CAY-1152:
---------------------------------
Description:
There's been a number of reports about this problem:
http://markmail.org/message/ihe7hf2sfzllda7a
http://markmail.org/message/u523nd24eb7nhzpm
If two DbEntities have the same name, but different schemas, Cayenne raises an exception (where?). We need to investigate this and make sure that Fully Qualified DbEntity name is used consistently throughlut the stack and the modeler.
Another subcase is outlined in CAY-1707 - 2 DbEntities have the same name, but are mapped to different DataNodes (so the schema might be implicit).
was:
There's been a number of reports about this problem:
http://markmail.org/message/ihe7hf2sfzllda7a
http://markmail.org/message/u523nd24eb7nhzpm
If two DbEntities have the same name, but different schemas, Cayenne raises an exception (where?). We need to investigate this and make sure that Fully Qualified DbEntity name is used consistently throughlut the stack and the modeler
> DbEntity schema is ignored when checking for DbEntity name uniqueness
> ---------------------------------------------------------------------
>
> Key: CAY-1152
> URL: https://issues.apache.org/jira/browse/CAY-1152
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
> Affects Versions: 3.0M5
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: Short term future
>
>
> There's been a number of reports about this problem:
> http://markmail.org/message/ihe7hf2sfzllda7a
> http://markmail.org/message/u523nd24eb7nhzpm
> If two DbEntities have the same name, but different schemas, Cayenne raises an exception (where?). We need to investigate this and make sure that Fully Qualified DbEntity name is used consistently throughlut the stack and the modeler.
> Another subcase is outlined in CAY-1707 - 2 DbEntities have the same name, but are mapped to different DataNodes (so the schema might be implicit).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira