From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Regarding useObjects |
Date: | 2023-09-27 10:17:37 |
Message-ID: | CADK3HHL7JGKre6r0xVTqAQg5Em1zC5McMrgr0v6Dudzfb0DybQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Wed, 27 Sept 2023 at 06:07, Achilleas Mantzios - cloud <
a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:
>
> On 9/27/23 12:55, Vladimir Sitnikov wrote:
>
> > So the problem with using float instead of Float is that it is
> impossible to have a null float and arrays can have nulls.
>
> There's a feature request for retrieving primitive arrays:
> https://github.com/pgjdbc/pgjdbc/issues/2939
>
> back in pre-postgresql-42* days we used to use -888 and -888.888 to
> represent int NULL and float NULL respectively, quite ...primitive but it
> worked. We should retain this old mapping , but once all systems are up to
> date we will start storing and reading NULLs in arrays as NULLs.
>
Using that mapping is not something that we would entertain.
If you are going to actually store NULL in the array, how would that work
with primitives ?
Dave
>
> Vladimir
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios - cloud | 2023-09-27 10:28:42 | Re: Regarding useObjects |
Previous Message | Achilleas Mantzios - cloud | 2023-09-27 10:07:39 | Re: Regarding useObjects |