Can this kind of set up be handled in Cayenne?
Yes.
It looks like multiple data maps could be used for a single data
node but can one data map be
used in multiple nodes, multiple domains or multiple projects?
Yes, you just need to configure it in cayenne.xml. One possible
solution is t
Thanks, Robert. That looks like a good plan.
Tony
-Original Message-
From: Robert Zeigler [mailto:robert.zeig...@roxanemy.com]
Sent: Tuesday, 14 April 2009 11:38 a.m.
To: user@cayenne.apache.org
Subject: Re: Validation
Constraint information is available by examining the ObjEntity and
Constraint information is available by examining the ObjEntity and
DbEntity objects corresponding to the given object class.
I used this in the tapestry5-cayenne integration module (t5cayenne)
to have tapestry automatically pick up the relevant data constraints
Note: currently, t5cayenne suppo
The documentation talks of removing validation as a concern of the GUI,
by using object validation that gets done before any commits. However,
validation can continue to be needed in the GUI since it is always nicer
to let users know of problems early on (such as the maximum length of a
value, that
We have two systems that have very similar database schemas. They are
not completely identical, however. To deal with this, currently, with
Hibernate, we have a set of common definitions (and classes), and a
separate set of definitions (and classes) for each specific system.
Hibernate can be config
I've reduced the data map to just what was necessary to replicate the
problem and have opened a new Jira issue, CAY-1208. I wasn't sure about
the severity, so left it as major. If I hit these problem during
production development, they would be show-stoppers, but I'm only
evaluating.
Cheers,
Tony
I think that sets a new record for responsiveness. I've frequently told a
story to open-source skeptics how I got a fix in only 3 hours. This one was
about 2:20. :-)
Yes, that fixes my test case on Oracle 8i. The SQL it generates now is:
SELECT DISTINCT t0.* FROM ROLE t0, EMPLOYEE_ROLE t1
In fact switching back to the legacy join syntax was already
accomplished for OpenBase (see OpenBaseJoinStack) :
https://issues.apache.org/jira/browse/CAY-1084
So I just cloned it for Oracle8:
https://issues.apache.org/jira/browse/CAY-1207
This code is committed, I just don't have a way to t
Thanks. About what I thought. Just wanted to check.
On Mon, Apr 13, 2009 at 12:41 PM, Mike Kienenberger wrote:
> By the way, when I say "could be added back in", I am not volunteering
> to do the work, only letting you know that you could probably figure
> out how to submit patches to do this
By the way, when I say "could be added back in", I am not volunteering
to do the work, only letting you know that you could probably figure
out how to submit patches to do this by looking at Cayenne 2 code and
porting to Cayenne 3.
On Mon, Apr 13, 2009 at 12:40 PM, Mike Kienenberger wrote:
> Yes,
Yes, you need Oracle 9 before that syntax is understood.
Oracle 8 only understands select * from t1, t2 where t1.x = t2.x. I
suppose the old oracle inner join support could be added back in.
Outer join support is even worse for 8, and not implementable for all
practical purposes.
On Mon, Apr 1
We have some apps running on an Oracle 8i database. Wow, almost 10 years
old. Cayenne 2 has been working great. When I tried updating to Cayenne 3,
I got a syntax error in a particular bit of SQL with a JOIN. This isn't an
urgent problem for us but I thought I'd mention it.
We have an Employee
On Apr 9, 2009, at 2:24 AM, Weddle, Anthony wrote:
EJBQL doesn't support subselects in the select clause or have
something
equivalent to the NVL function, so we'd have to do things differently.
Correct.
However, I wondered if it could cope with the first subselect and so
ended up with this
13 matches
Mail list logo
