> On Jun 15, 2020, at 11:47 PM, Dirk Lattermann wrote:
>
> On Mon, 15 Jun 2020 14:49:05 +0300
> Andrus Adamchik wrote:
>
>>> On Jun 9, 2020, at 5:54 PM, John Huss wrote:
>>>
>>> 2) Regarding skipping parsing when just going straight back out
>>> again to serialization - I have felt the rel
On Mon, 15 Jun 2020 14:49:05 +0300
Andrus Adamchik wrote:
> > On Jun 9, 2020, at 5:54 PM, John Huss wrote:
> >
> > 2) Regarding skipping parsing when just going straight back out
> > again to serialization - I have felt the reluctance (like you) of
> > parsing this in those cases. But one thing
Yeah, sounds good! Thanks!
On Mon, Jun 15, 2020 at 7:22 AM Malcolm Edgar
wrote:
> That sounds like a great approach to me.
>
> regards Malcolm
>
> On Mon, Jun 15, 2020 at 9:49 PM Andrus Adamchik
> wrote:
>
> >
> >
> > > On Jun 9, 2020, at 5:54 PM, John Huss wrote:
> > >
> > > 2) Regarding skip
That sounds like a great approach to me.
regards Malcolm
On Mon, Jun 15, 2020 at 9:49 PM Andrus Adamchik
wrote:
>
>
> > On Jun 9, 2020, at 5:54 PM, John Huss wrote:
> >
> > 2) Regarding skipping parsing when just going straight back out again to
> > serialization - I have felt the reluctance (
> On Jun 9, 2020, at 5:54 PM, John Huss wrote:
>
> 2) Regarding skipping parsing when just going straight back out again to
> serialization - I have felt the reluctance (like you) of parsing this in
> those cases. But one thing to think about is that the parser/serializer
> (let's say Jackson i
As promised, here is the module that I wrote [1] integrating Wkt, GeoJSON and
TimestampRange types [2] with Cayenne 4.2. The integration is done via a custom
adapter [3] that installs extended types and a custom SQLTreeProcessor [4].
Whatever effort happens on Cayenne site, it can freely borrow
un 9, 2020 at 1:59 AM Andrus Adamchik
>>> wrote:
>>>
>>>> Hi John, Malcom --
>>>>
>>>> (Don't know if Malcom is on dev@, so posting it here; we can move to
>> dev@)
>>>>
>>>> Looks like the need for JSON type and other non-standard
independently by at least 3 community members can result in
> >> something that we can bring to the Cayenne core. Let's discuss how this
> >> might work.
> >>
> >> So... We'd need to create a taxonomy of "value object" types that map to
>
ers. More than one adapter can support a given type.
> Also we need to add adapter-specific logic to db-import Types.OTHER as the
> right value object type using DB-specific metadata of a given column. Same
> for SQL schema generation - for Types.OTHER we can derive the true type
> bas
g that we can bring to the Cayenne core. Let's discuss how this
>> might work.
>>
>> So... We'd need to create a taxonomy of "value object" types that map to
>> "java.sql.Types.OTHER" (e.g. Jsonb, Wkt, TimestampRange, etc.). Then we'd
>>
; corresponding DbAdapters. More than one adapter can support a given type.
> Also we need to add adapter-specific logic to db-import Types.OTHER as the
> right value object type using DB-specific metadata of a given column. Same
> for SQL schema generation - for Types.OTHER we can d
ExtendedTypes for each one of them, and register them inside the
corresponding DbAdapters. More than one adapter can support a given type. Also
we need to add adapter-specific logic to db-import Types.OTHER as the right
value object type using DB-specific metadata of a given column. Same for SQL
sc
12 matches
Mail list logo