| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Martin Handsteiner <martin(dot)handsteiner(at)sibvisions(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-jdbc(at)lists(dot)postgresql(dot)org" <pgsql-jdbc(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: stringtype=unspecified is null check problem |
| Date: | 2023-01-12 14:36:44 |
| Message-ID: | CADK3HHJbx5+DxndG--8FKDF3uAOLS3MtFGu++73TEvkFeABpqA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 12 Jan 2023 at 03:32, Martin Handsteiner <
martin(dot)handsteiner(at)sibvisions(dot)com> wrote:
> Thanks a lot, I think, this will help a lot of (java) users, and makes the
> usage of PostgreSQL DB a way better!
>
> I had yesterday an idea for a solution on java side. As we have already a
> preprocessing with a jdbc wrapper, for function and procedure calls (in/out
> parameters are not working with postgres jdbc), I'll added preprocessing
> for the parameters.
>
> I'll search the statement for all question marks (?) that are not inside a
> comment (-- \n, /* */), not in quotes (" ") and not in strings (' '), check
> the parameter, if it is null, and replace the ? by null, and reduce the
> parameter list.
>
> I can link the code if you want, as it is Apache License 2.0.
>
Please do
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sz-liva | 2023-01-12 17:45:43 | [pgjdbc/pgjdbc] b840bf: fix: improve thread safety of PgResultSet#getTimes... |
| Previous Message | Dave Cramer | 2023-01-12 13:41:47 | [pgjdbc/pgjdbc] |