From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Rémi Aubel <remi(dot)aubel(at)gmail(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: "could not determine data type of parameter" with timestamp |
Date: | 2017-12-05 20:42:54 |
Message-ID: | CAKFQuwarUwHAX6Zss4Cqdu2i8Y4nsTfRpz9x9atgudnfia_aew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Tue, Dec 5, 2017 at 8:11 AM, Rémi Aubel <remi(dot)aubel(at)gmail(dot)com> wrote:
> Hello,
>
> I know my problem has already been answered in this list (
> https://www.postgresql.org/message-id/CA%2BxsaB0EMDaNek0Oky9c17_8UX3-
> epWVP11%2BvTNgrAPoY2s9FA%40mail.gmail.com), but it was a long time ago
> and I would like to know if any other solution exists now.
>
Not that I am aware.
> But this workaround is not really useful for me, because my application
> uses generated (dynamic) queries and targets multiple database types (not
> only PosgreSQL). So, when I know the targeted database, I do not know my
> parameter types anymore.
>
I'd probably perform the null test in Java and pass the true/false boolean
result along to the query:
SELECT * FROM my_table WHERE ?::bool;
ps.setBoolean(1, tsvar = null); //my Java is rusty but you get the idea.
That should work in any database.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2017-12-06 00:57:45 | Re: "could not determine data type of parameter" with timestamp |
Previous Message | Rémi Aubel | 2017-12-05 20:33:51 | Re: "could not determine data type of parameter" with timestamp |