On 25/09/09 5:37 AM, Lawrence Gerstley wrote:
Also, just an FYI: the Wiki link on the home page seems to be quite dead.
I've been trying to fix it, but something in the Confluence exporter is just
breaking it every time. Argh...
Ari
--
-->
Aristedes Maniatis
GPG fin
Just following the earlier documentation, and trying to describe to a
team how they can elevate an individual query for debugging purposes.
To whit (from the 2.0 documentation):
When SQL tracing is turned off, it is possible to log the execution of
only certain queries or commits by manual
Per query logging levels existed in the early versions of Cayenne, but
got killed quite some time ago. IMO, though occasionally convenient,
this goes against good logging practices. What case are you trying to
address with it?
Andrus
On Sep 24, 2009, at 10:37 PM, Lawrence Gerstley wrote:
Hi,
I've been searching through documentation and Googling for some time
to see how to elevate the logging level of an individual query, and
came across the type of function is was looking for, but which seems
to be more hypothetical than real (i.e., it's not in the Query object):
SelectQ
I faked vertical inheritance on a previous project. It is a little
more manual/tedious, but works. Mostly. I had to manually manage the
relationships (such as when I created a new subclass instance, create
the superclass instance/relationship at the same time). You could use
a listener/callback
Crap. OK. Nothing like an occasional reminder of what happens when you
assume things.
Thanks for the tip Michael-- I'll just use another method for now.
Dave
On Thu, Sep 24, 2009 at 1:18 PM, Michael Gentry wrote:
> I believe single-table and horizontal have been implemented, but I
> don't thi
I believe single-table and horizontal have been implemented, but I
don't think vertical has been implemented yet. There is still an open
ticket for vertical inheritance:
https://issues.apache.org/jira/browse/CAY-1090
On Thu, Sep 24, 2009 at 1:59 PM, Dave Lamy wrote:
> Yes, I'm attempting verti
Yes, I'm attempting vertical multiple-table inheritance. I was assuming
functionality based upon this document:
http://cayenne.apache.org/doc/inheritance-overview.html
which had this section:
Vertical (joined) inheritance
This final approach requires one table per subclass plus one table for th
You are trying to do multiple-table inheritance?
Unless I'm mistaken, I don't believe that has been implemented yet.
Cayenne can do in-table inheritance using a discriminator column.
On Thu, Sep 24, 2009 at 1:10 PM, Dave Lamy wrote:
> Hey guys--
>
> I'm attempting to model some inheritance for
Hey guys--
I'm attempting to model some inheritance for the first time and it's not
working yet. Here's my situation:
My model is to have a non-abstract parent class->table and then
subclass->tables like so:
First I should doublecheck to make sure my mapping XML looks OK:
...
Thanks for the reply on this Andrey-- sorry for the delay in expressing my
gratitude :-).
I've gotten pulled away from this little nugget for the time being, but will
be sure to update when I have a chance to give it a go.
Dave
On Thu, Sep 17, 2009 at 2:26 PM, Andrey Razumovsky <
razumovsky.and.
You first enable JGroups in oscache.properties per OSCache docs:
http://www.opensymphony.com/oscache/wiki/Clustering.html
And then in your postUpdate/postRemove/postPersist listener you call
dataContext.getQueryCache().removeGroup("groupName");
"groupName" should be the same String you are u
12 matches
Mail list logo