Bug #3241
schema conversion only allows _user table in one schema
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
History
#1 Updated by Eric Faulhaber over 7 years ago
Schema conversion will create the meta_user
(converted name for _user
table) in the schema of only the first namespace
configured in p2j.cfg.xml
. Subsequent schemata will not have the table created. I think the table needs to be created in each schema configured for a project.
The limitation seems to have been implemented purposefully, but I'm not sure why. Further investigation is needed.
I worked around this limitation in a recent customer project by moving the namespace
node for which the _user
table was needed to the first position in the XML node, but that only worked because the table was not needed for any other databases in this particular project.