Really? When I try to set the same name for both DBEntities, the modeler turns the name field red and shows a tooltip message "There is another entity with the name...".
Oh, it must be only a modeler quirk. If I change the name by editing the DataMap file directly, it works. And I can load the DataMap in the modeler afterward. Thanks again. On Thu, May 17, 2012 at 1:38 PM, Michael Gentry <[email protected]>wrote: > I thought the table names could be duplicated as long as the class > names were unique? > > > On Thu, May 17, 2012 at 1:18 PM, Bryan Lewis <[email protected]> > wrote: > > Rockin'! Works like a charm. The only drawback was that the table name > in > > the second database needs to be unique, but I can work around that by > > renaming the conflicting table on my side. > > > > Thanks! > > > > > > On Thu, May 17, 2012 at 9:31 AM, Michael Gentry <[email protected] > >wrote: > > > >> Hi Bryan, > >> > >> I'm not sure you need two DataDomains. Have you tried: > >> > >> DataDomain > >> DataMapForDB1 > >> DataNodeForDB1 > >> DataMapForDB2 > >> DataNodeForDB2 > >> > >> Then make sure that the DataNode for DataMapForDB1 is DataNodeForDB1 > >> and the DataNode for DataMapForDB2 is DataNodeForDB2. > >> > >> mrg > >> > >> > >> On Thu, May 17, 2012 at 8:06 AM, Bryan Lewis <[email protected]> > >> wrote: > >> > We need to fetch objects from a second database. (That is, query an > >> entity > >> > in a second domain.) I've tried a couple of quick things -- putting > two > >> > domains in one cayenne.xml project -- but I've been unable to make it > >> work, > >> > in Cayenne 3.0.2 anyway. > >> > > >> > I found CAY-1318 which says, "Multi-datadomain runtime configurations > >> offer > >> > no advantage over multiple configurations with a single domain each. > So > >> > going to change the project structure to only support a single > >> > DataDomain." It says it was fixed in 3.1. > >> > > >> > So if we upgrade to 3.1 will we have an easier time? Are there any > >> > examples of querying from multiple configurations? > >> > > >> > Thanks, > >> > Bryan Lewis > >> >
