Here is latest version that already committed and can be tested:
ObjectSelect
.columnQuery(Artist.class,
Property.createSelf(Artist.class),
// query root
Artist.PAINTING_ARRAY.dot(Painting.GALLERY), // toOne relationship
Artist.PAINTING_ARRAY.f
> On Mar 16, 2017, at 11:14 AM, Nikita Timofeev
> wrote:
>
> On Mon, Mar 13, 2017 at 3:05 PM, Aristedes Maniatis wrote:
>> On 13/3/17 9:53pm, Andrus Adamchik wrote:
>>>
On Mar 13, 2017, at 1:46 PM, Aristedes Maniatis wrote:
Just a wild thought, but would this syntax be
On Mon, Mar 13, 2017 at 3:05 PM, Aristedes Maniatis wrote:
> On 13/3/17 9:53pm, Andrus Adamchik wrote:
>>
>>> On Mar 13, 2017, at 1:46 PM, Aristedes Maniatis wrote:
>>>
>>>
>>> Just a wild thought, but would this syntax be helpful...
>>>
>>> List result = ObjectSelect.query(Artist.class)
>>>
On 13/3/17 9:53pm, Andrus Adamchik wrote:
>
>> On Mar 13, 2017, at 1:46 PM, Aristedes Maniatis wrote:
>>
>>
>> Just a wild thought, but would this syntax be helpful...
>>
>> List result = ObjectSelect.query(Artist.class)
>> .addColumns(Artist.PAINTING_COUNT)
>> .select(context);
>>
>> So
> On Mar 13, 2017, at 1:46 PM, Aristedes Maniatis wrote:
>
>
> Just a wild thought, but would this syntax be helpful...
>
> List result = ObjectSelect.query(Artist.class)
> .addColumns(Artist.PAINTING_COUNT)
> .select(context);
>
> So then we are adding more columns to the existing Da
On 13/3/17 7:26pm, Andrus Adamchik wrote:
>
> Yep. A typical use case for intermixing DataObjects and scalars in the result
> is this: [, ] that gives us each object's to-many
> counts without resolving to-many relationships. What I am unsure though is
> whether [, ] result is of any use to any
>
> What is the output of this:
>
> result = ObjectSelect.query(Artist.class)
>.columns(createSelf(Artist.class))
>.select(context);
>
> Is that the same as
>
> result = ObjectSelect.query(Artist.class)
>.select(context);
>
> would the generated SQL be the same?
>
Small com
> Oh, I get it now. You are suggesting in option (2) that Cayenne creates a
> CROSS JOIN in sql.
Actually not a CROSS join. It will be a regular INNER JOIN based on
relationship from the query root. JPA spec defines CROSS join operations. We
don't (yet?).
> Sometimes you want to fetch specific
On 13/3/17 5:57pm, Andrus Adamchik wrote:
>
List result = ObjectSelect.query(Artist.class)
.columns(Artist.ARTIST_NAME, Artist.PAINTING_ARRAY)
.select(context);
>
>
>>> For me it's not clear when do we need direct List result for toMany
>>> relationship instead of
>>>
>>> List result = ObjectSelect.query(Artist.class)
>>> .columns(Artist.ARTIST_NAME, Artist.PAINTING_ARRAY)
>>> .select(context);
>> For me it's not clear when do we need direct List result for toMany
>> relationship instead of using Prefetch (or even selecting related
>> entitie
> On Mar 9, 2017, at 10:17 AM, Nikita Timofeev
> wrote:
>
> On Wed, Mar 8, 2017 at 3:48 AM, Aristedes Maniatis wrote:
>> On 7/3/17 11:12pm, Nikita Timofeev wrote:
>>> 2) Add new factory methods in Property class:
>>>
>>> Property createSelf(Class type);
>>
>> Why wouldn't we just use nor
On Wed, Mar 8, 2017 at 3:48 AM, Aristedes Maniatis wrote:
> On 7/3/17 11:12pm, Nikita Timofeev wrote:
>> 2) Add new factory methods in Property class:
>>
>> Property createSelf(Class type);
>
> Why wouldn't we just use normal constructors?
>
> a = new Property(Artist.class);
That's because c
On 7/3/17 11:12pm, Nikita Timofeev wrote:
> 2) Add new factory methods in Property class:
>
> Property createSelf(Class type);
Why wouldn't we just use normal constructors?
a = new Property(Artist.class);
> Property createForRelationship(
>Property property, Class
13 matches
Mail list logo
