Yeah, I guess we can make an assumption here... Feel free to open a Jira.
Andrus
On Jan 19, 2011, at 8:16 PM, David Balažic wrote:
> Yes, but a function return is always direction OUT, isn't it?
>
> David
>
>
>> -Original Message-
>> From: Andrus Adamchik [mailto:and...@objectstyle.or
Yes, but a function return is always direction OUT, isn't it?
David
> -Original Message-
> From: Andrus Adamchik [mailto:and...@objectstyle.org]
> Sent: Wednesday, January 19, 2011 6:56 PM
> To: user@cayenne.apache.org
> Subject: Re: Modeller - reenginered functions parameters
> Import
Unfortunately reverse engineering completely depends on the metadata provided
by the driver, which means Cayenne often gets incomplete information, that has
to be filled by the user manually. I suspect this is what happened here as well.
Andrus
On Jan 19, 2011, at 6:43 PM, David Balažic wrote:
>
> Is there anything special I should look out for?
The scope of the change (and possibly thread safety) are the things to watch
for. Cayenne mapping is usually application-scoped and shared by all contexts
and all threads. So your tweak should probably have the same scope.
Andrus
On Jan 1
Hi!
When reengineering a DB, including stored prodcedures,
the first parameter of functions is like this:
No.: R
Name: _return_value
Direction:
Type Other:
Max Length:
Precision:
The thing is, Direction is empty.
When saving, the modeller gives a warning:
ProcedureParameter has no direction.
Lo
Hi!
I tried putting the fix between
Procedure proc =
context.getEntityResolver().getProcedure("cayenne_tst_select_proc");
and
ProcedureQuery query = new ProcedureQuery(proc);
This way I don't need any special context setup.
It appears to work. I just copied over the content
of OracleStackAdapt
You can emulate joint prefetching via SQLTemplates. It requires the correct
labels for prefetched entity in the result, in the form of
relationshipname.COLUMN_NAME. Not sure how practical this is to configure, but
the framework has this ability.
Andrus
On Jan 19, 2011, at 12:22 PM, Bruno René
Hello all,
I have a query defined on the modeler which is fetched to a known data
object. Is there any way to perform a join (or prefetch) for another
data object that I know I will have to access too?
Thanx & Regards
Bruno
