On 29/01/2010, at 9:50 PM, Andrus Adamchik wrote:
> Sorry, there's too many things going on in Cayenne right now. This one is a
> very important discussion, but I guess I have to drop the ball on it for now.
> We'll definitely get back to it, but I suggest we don't jira anything yet, as
> the p
Sorry, there's too many things going on in Cayenne right now. This one
is a very important discussion, but I guess I have to drop the ball on
it for now. We'll definitely get back to it, but I suggest we don't
jira anything yet, as the plan is not yet clear, and too-high level
Jiras are not
Hi Andrus,
just following this up again. Just a few questions:
a) is it also worth also thinking about the ability to specify the join-type in
the model for a relationship in order to specify what's the default?
b) is there any further discussion needed to identify necessary jira tasks?
On 15/0
On Jan 15, 2010, at 11:05 AM, Andrus Adamchik wrote:
* ASTs are generic and not very intuitive for direct manipulation in
API. A good analogy would be DOM trees vs. real object models
represented by those trees.
* ASTs often have slight differences in structure compared to an
ideal domai
On Jan 14, 2010, at 11:40 AM, Aristedes Maniatis wrote:
Come to think of it, what is the difference between your new Key
typesafe class and Path, other than a few dots...
One is a "domain object", and the other one is a DSL expression (see
below).
Bridging that distinction is actually
On 14/01/2010, at 8:40 PM, Aristedes Maniatis wrote:
> On 14/01/10 8:10 PM, Andrus Adamchik wrote:
>>
>> Artist.PAINTINGS.dot(Painting.EXHIBITS).alias("X").dot(Exhibit.GALLERIES).eq("Y");
>
> This is a long way from obvious for the most common use of the syntax:
> combining AND queries across a
On Jan 14, 2010, at 11:40 AM, Aristedes Maniatis wrote:
Sure named aliases might be useful in themselves, maybe, for
someone. I can't personally think of a reason.
You are not using EJBQL (not that it is very usable in 3.0). It has an
explicit notion of named joins. This is where it all f
On 14/01/10 8:10 PM, Andrus Adamchik wrote:
On Jan 13, 2010, at 2:38 PM, Aristedes Maniatis wrote:
I've tried to explain the current usage better in the docs, given what
I now understand. Please let me know if I misunderstood something. I
had originally thought they were there as shortcuts to
doh, was going to send this to dev...
On Jan 14, 2010, at 11:10 AM, Andrus Adamchik wrote:
On Jan 13, 2010, at 2:38 PM, Aristedes Maniatis wrote:
I've tried to explain the current usage better in the docs, given
what I now understand. Please let me know if I misunderstood
something. I ha
[
https://issues.apache.org/cayenne/browse/CAY-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik closed CAY-802.
---
Resolution: Fixed
Fix Version/s: 3.0
> Split Expressi
d of pipe notation):
http://objectstyle.org/cayenne/lists/cayenne-devel/2008/04/0134.html
> Split Expressions
> -
>
> Key: CAY-802
> URL: https://issues.apache.org/cayenne/browse/CAY-802
> Project: Cayenne
>
Split Expressions
-
Key: CAY-802
URL: https://issues.apache.org/cayenne/browse/CAY-802
Project: Cayenne
Issue Type: New Feature
Components: Cayenne Core Library
Reporter: Mike Kienenberger
Sorry, I probably misunderstood your previous explanation:
"Split expressions are going to be critical to implementing
useful outer joins."
The changes I've made to CAY-514 are undone. What I was trying to do
(but probably did it wrong) is to categorize Jira's acc
Andrus,
I don't think this is quite the same thing.
Split expressions are probably part of the solution to this problem,
but not the entire solution. Nor did this feature have to be
implemented in order to have useful outer joins.
I'd recommend reverting your change to this Jira
14 matches
Mail list logo
