Hi all, I have just begun using Transfer. I've been a CF developer
since 2001, having trudged through countless CRUD scenarios, so
needless to say I'm anxious to leverage Transfer. That being said,
there is a configuration issue that currently forces me to hardcode
different prefixes into my transfer.xml.
I develop an internal web portal used by a number of groups in my
company. Internally it always uses the same schema, however the
portal is deployed and installed on a number of disparate
environments. This often results in different schema owners for each
deployment.
Example:
my own deployment uses portal.{table}
A colleagues deployment uses core.{table}
I want to deploy Transfer as part of my web portal, but due to the
difference in schema I would be forced to have my clients change the
table property of every object in transfer.xml. A prefix / schema
property in datasource.xml is the ideal solution. I'm surprised there
was no mention of this issue (that I could find) other than here where
the solution was to prepend the schema name to objects in
transfer.xml.
Does everyone else just keep multiple copies of transfer.xml in these
scenarios?
http://groups.google.com/group/transfer-dev/browse_thread/thread/89f00e68bbd6c6bc/fa287d5756a22f54?lnk=gst&q=prefix#fa287d5756a22f54
Thanks!
Kerr
--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer
You received this message because you are subscribed to the Google Groups
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
