in my setup or procedure, an undocumented
quirk of flattened relationships, or a bug in Cayenne?
Thanks for any help you can give.
-Tad
Thanks! We did figure out a fix on our own; setting the "nullify" delete
rule on the relationship from child to parent fixes the issue.
Really, "nullify" should be the default... but I digress.
--
Thanks,
Tad
On Wed, Feb 22, 2012 at 2:35 PM, Michael Gentry wrote:
> Hi T
orrect that we need to perform an explicit query in
order to refresh this list, rather than using the generated getter?
Thanks for any help.
--
Thanks,
Tad
know not to
apply these changes to the database schema.
Is there a way to suppress this behavior? Perhaps by ignoring the view
entirely, or adding something to the view definition itself to assign the
"primary key" attribute to a column of its results?
Thanks for any help.
-Tad Fisher
I'd add to the list the ability to select a subset of tables to
reverse-engineer.
I can't reproduce it using disjoint prefetch semantics anymore. I
suspect my Eclipse/Tomcat instance was at fault.
--
Thanks,
Tad
On Tue, Jul 19, 2011 at 8:26 PM, Andrus Adamchik wrote:
> It really shouldn't make a difference.
>
> So if you fetch the data outside Cayenne
I solved the issue by setting JOINT_PREFETCH_SEMANTICS on the
prefetch. Why should this make a difference?
--
Thanks!
Tad
trategy(QueryCacheStrategy.NO_CACHE);
return getObjectContext().performQuery(query);
What am I doing wrong here?
--
Thanks!
Tad
ships with the existing ones. If I make a
schema change within the modeler, it wants to drop all of the tables
Cayenne doesn't know about, and I have to manually scan and ignore
these entries.
--
Thanks,
Tad Fisher
