Thanks Nikita, at least I know I'm not doing anything wrong then :) - hugi
> On 24 May 2017, at 14:52, Nikita Timofeev <ntimof...@objectstyle.com> wrote: > > Hi Hugi, > > Seems like custom types are broken in ColumnSelect, I see this bug in > my test too. > > On Wed, May 24, 2017 at 5:34 PM, Hugi Thordarson <h...@karlmenn.is> wrote: >> I'm using today's version of 4.0.M6-SNAPSHOT. Always living on the edge :) >> >> - hugi >> >> >>> On 24 May 2017, at 14:31, Andrus Adamchik <and...@objectstyle.org> wrote: >>> >>> Or .. if you already have cayenne-java8 in your app, and the problem is >>> specific to just the column select query, you may also need to switch to >>> M6. IIRC there were some issues in M5 with the behavior that you describe. >>> >>> Andrus >>> >>>> On May 24, 2017, at 5:28 PM, Andrus Adamchik <and...@objectstyle.org> >>>> wrote: >>>> >>>> You need to add cayenne-java8 dependency. >>>> >>>> Unfortunately the fallback behavior (treat unknown class as Serializable) >>>> is extremely confusing. Though I think we log some warnings before doing >>>> that. >>>> >>>> ANdrus >>>> >>>> >>>>> On May 24, 2017, at 5:20 PM, Hugi Thordarson <h...@karlmenn.is> wrote: >>>>> >>>>> Hi all, >>>>> if I try to fetch Java 8 date objects using ColumnSelect, the values get >>>>> returned as byte arrays instead of actual objects. Example: >>>>> >>>>> LocalDateTime creationDate = ObjectSelect >>>>> .query( User.class ) >>>>> .column( User.CREATION_DATE ) >>>>> .selectFirst( Jambalaya.newContext() ); >>>>> >>>>> User.creationDate() is a LocalDateTime—but the fetch will fail since the >>>>> returned value is a byte array. >>>>> >>>>> Bug? >>>>> >>>>> Cheers, >>>>> - hugi
