[
http://jira.nuxeo.org/browse/NXP-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume updated NXP-3588:
-----------------------------------
Fix Version/s: (was: 5.2.1)
5.2.x
> Allow changing VCS table names to avoid clashes
> -----------------------------------------------
>
> Key: NXP-3588
> URL: http://jira.nuxeo.org/browse/NXP-3588
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Core SQL Storage
> Affects Versions: 5.2 GA
> Reporter: Nel Taurisson
> Assignee: Florent Guillaume
> Fix For: 5.2.x
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> VCS / SQLDirectory name clash:
> If you have an sql directory named "foo" mapped on table "foo" and a document
> schema with, somewhere in it, a complex type called "foo". VCS creates a
> table named "foo" for the complex type property. Then when the directory is
> accessed, the directory service wants to drop the table, and for a reasion I
> havent analyze the application freezes (at least with postgresql, the DROP
> TABLE never returns...).
> Looking at the tables crearted by VCS, when a name clash is detected for a
> complex type, then the table is prefixed with the schema name. But in the
> case described above, the name clash isn't detected because the directory is
> "lazy created".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
