Probably we will do the same
On 2020/06/10 20:06:12, John Huss wrote:
> For what it is worth, I often run pre-release versions in production. I am
> not running 4.2.M1 yet, but have tested it a lot and have not had any
> problems.
>
> On Wed, Jun 10, 2020 at 2:28 PM Andrea Biasillo wrote:
>
>
Probably we will do the same
On 2020/06/11 00:31:41, Lon Varscsak wrote:
> I am running 4.2.M2-SNAPSHOT 🤫 in production :P
>
> On Wed, Jun 10, 2020 at 1:06 PM John Huss wrote:
>
> > For what it is worth, I often run pre-release versions in production. I am
> > not running 4.2.M1 yet, but have
I am running 4.2.M2-SNAPSHOT 🤫 in production :P
On Wed, Jun 10, 2020 at 1:06 PM John Huss wrote:
> For what it is worth, I often run pre-release versions in production. I am
> not running 4.2.M1 yet, but have tested it a lot and have not had any
> problems.
>
> On Wed, Jun 10, 2020 at 2:28 PM An
For what it is worth, I often run pre-release versions in production. I am
not running 4.2.M1 yet, but have tested it a lot and have not had any
problems.
On Wed, Jun 10, 2020 at 2:28 PM Andrea Biasillo wrote:
> Hi Andrus!
>
> Thanks for the response, so it will be not too soon. We really need t
Hi Andrus!
Thanks for the response, so it will be not too soon. We really need the new
sub-query functionality. We are testing and using 4.2.M1 and so far seems great.
Andrea
On 2020/06/10 06:33:14, Andrus Adamchik wrote:
> Hi Andrea,
>
> As you may know, there is a 4.2.M1 now. I suspect the
Clear now.
> On Jun 10, 2020, at 5:53 PM, John Huss wrote:
>
> On Wed, Jun 10, 2020 at 1:25 AM Andrus Adamchik
> wrote:
>
>>> Would this also address the use case where the DB doesn't have a special
>>> type (like JSONB) and just stores it as a plain varchar or byte[], but
>> you
>>> still wan
On Wed, Jun 10, 2020 at 1:25 AM Andrus Adamchik
wrote:
> > Would this also address the use case where the DB doesn't have a special
> > type (like JSONB) and just stores it as a plain varchar or byte[], but
> you
> > still want the Java side to treat it as a complex object?
>
> Yep. I did this i
Hi All,
For my use case I was simply looking for Java String mapping to underlying
MySQL (JSON data type) and Postgres (JSON or JSONB data types). I would
generally be rendering this JSON text directly in a REST API, and not going
through Java complex object serialization pipeline.
I think if pe
