Thank you Andrus, I was working on it for ages, and then started to
run out of time and rewrote the code to do the join in the code rather
than the DB as the number of records in each table was not very large.
I will give it a try with the schemas in both DataMaps and see how I
go. I did have the 2
In our case it turned out a relationship query with a join across DataNodes.
Since both DBs were on the same server, and such join was supported in theory,
it was fixed by specifying schemas for all tables in 2 DataMaps. If the DBs are
on different servers and joins are not possible, I guess you
Gary,
just stumbled on something similar in one of our client projects.
Investigating... Stay tuned.
Andrus
On Jun 12, 2012, at 10:48 AM, Andrus Adamchik wrote:
> But what happens inside SelectQuery.route(..)? (the failing query is
> SelectQuery, right?). This is where the DataNode to Query
But what happens inside SelectQuery.route(..)? (the failing query is
SelectQuery, right?). This is where the DataNode to Query mapping logic is, so
this is the place to look for clues.
Andrus
On Jun 6, 2012, at 11:47 AM, Gary Jarrel wrote:
> I've been debugging & debugging, and for the life of
I've been debugging & debugging, and for the life of me I can not find
where the fault is, both DataNodes are set correctly, I just can't
seem to see what I am missing. :(
Any further thoughts?!
Gary
On Tue, Jun 5, 2012 at 10:41 PM, Gary Jarrel wrote:
> Just tried it with an XMLPoolingDataSourc
Just tried it with an XMLPoolingDataSourceFactory and got the same
error. To the debugger it is!
On Tue, Jun 5, 2012 at 10:06 PM, Gary Jarrel wrote:
> Thank you Andrus, I'll run it through a debugger and see what could be
> causing it, I also try perhaps using an XMLPoolingDataSourceFactory to
>
Thank you Andrus, I'll run it through a debugger and see what could be
causing it, I also try perhaps using an XMLPoolingDataSourceFactory to
see if it makes a difference. Will advise!
G
On Tue, Jun 5, 2012 at 10:01 PM, Andrus Adamchik wrote:
>
>> I am also using CayenneFilter to initialize Caye
> I am also using CayenneFilter to initialize Cayenne,
This is fine.
> but I think I was reading in one of the previous threads that CayenneFilter
> is simple
> and in more complex situations Srging or Guice should be used to initialize.
I'd rephrase this advice as "Cayenne can be used with a
Also could it have something to do with the fact that I have a
flattened relationship from an entity jayExtranet to an etity in jay
which goes via a many-to-many relationship table in the jayExtranet
datasource?
G
On Tue, Jun 5, 2012 at 9:45 PM, Gary Jarrel wrote:
> Hi Andrus,
>
> No there are n
Hi Andrus,
No there are not!
I am also using CayenneFilter to initialize Cayenne, but I think I was
reading in one of the previous threads that CayenneFilter is simple
and in more complex situations Srging or Guice should be used to
initialize. I've also read that there is only 1 ServerRuntime is
g that 'dbo.client_contracts' comes from jay data
> source.
>
> Thank you
>
> Gary
> On Tue, Jun 5, 2012 at 9:14 PM, Bryan Lewis wrote:
>> I got cross-database queries working just recently, with a boost from
>> Michael Gentry. I'd guess the culprit is
'dbo.client_contracts' comes from jay data
source.
Thank you
Gary
On Tue, Jun 5, 2012 at 9:14 PM, Bryan Lewis wrote:
> I got cross-database queries working just recently, with a boost from
> Michael Gentry. I'd guess the culprit is that your nodes are missing the
>
I got cross-database queries working just recently, with a boost from
Michael Gentry. I'd guess the culprit is that your nodes are missing the
datasource. For example:
wrote:
> Hi Guys,
>
> Just started a new project using Cayenne 3.1M3 set up some test code
> to see whet
Hi Guys,
Just started a new project using Cayenne 3.1M3 set up some test code
to see whether I can get the cross database queries to work, but it
seems that every time I run a query across the 2 database it tries to
use the 1 database and hence crashes out with
14 matches
Mail list logo
