> This one fixed too. Waiting for the next one :)
Works like a charm—saved the day, thanks!
>> Yes, that's right :) I see this now in my test too, code path that I
>> don't like (and that is hard to step on) bites again.
Yeah, I tend to be good at hitting those :)
Have a nice weekend,
- hugi
This one fixed too. Waiting for the next one :)
On Fri, May 26, 2017 at 4:03 PM, Nikita Timofeev
wrote:
> Yes, that's right :) I see this now in my test too, code path that I
> don't like (and that is hard to step on) bites again.
>
> On Fri, May 26, 2017 at 3:53 PM, Hugi Thordarson wrote:
>> Th
Yes, that's right :) I see this now in my test too, code path that I
don't like (and that is hard to step on) bites again.
On Fri, May 26, 2017 at 3:53 PM, Hugi Thordarson wrote:
> That's always fun :). BarCode.CODE is a LONGVARCHAR mapped to a TEXT-column
> in a MySQL db.
>
> - hugi
>
>
>> On 2
That's always fun :). BarCode.CODE is a LONGVARCHAR mapped to a TEXT-column in
a MySQL db.
- hugi
> On 26 May 2017, at 12:48, Nikita Timofeev wrote:
>
> Yes, fix definitely affected this query, but seems that it's not broke
> something, but rather revealed some other hidden bug.
> What is the
Yes, fix definitely affected this query, but seems that it's not broke
something, but rather revealed some other hidden bug.
What is the type of DbAttribute mapped on BarCode.CODE property?
On Fri, May 26, 2017 at 3:37 PM, Hugi Thordarson wrote:
> Is it possible the fix broke something else? I'm
Is it possible the fix broke something else? I'm now getting exceptions for
queries that worked this morning. I only see it happening in queries where i'm
traversing to-many relationships in the where-part of the query though. This
method:
public String number() {
return
Awesome, thanks! Works like a charm.
- hugi
> On 26 May 2017, at 11:56, Nikita Timofeev wrote:
>
> Hi again,
>
> I've pushed fix for this issue.
> https://github.com/apache/cayenne/commit/eac1f31073045fec6eafef3f3fd6cb05f0201994
>
> On Wed, May 24, 2017 at 7:03 PM, Hugi Thordarson wrote:
>>
Hi again,
I've pushed fix for this issue.
https://github.com/apache/cayenne/commit/eac1f31073045fec6eafef3f3fd6cb05f0201994
On Wed, May 24, 2017 at 7:03 PM, Hugi Thordarson wrote:
> Thanks Nikita, at least I know I'm not doing anything wrong then :)
>
> - hugi
>
>
>> On 24 May 2017, at 14:52, Ni
Hi Hugi,
You remembering this correctly, this was possible in 4.0M5.
Since 4.0.M6 there is API to select whole objects via column select.
It is working by default for toOne relationships,
for collections there is new method in Property flat(Class), that
will return "flat" array of objects.
So you
Hi all,
I seem to recall that it was possible to fetch to-many relationships using
ColumnSelect. However, if I attempt to do something like this…
public static void main( String[] args ) {
List list = ObjectSelect
.query( Receipt.class )
.co
10 matches
Mail list logo
