| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Rémi Aubel <remi(dot)aubel(at)gmail(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: "could not determine data type of parameter" with timestamp |
| Date: | 2018-03-29 13:42:17 |
| Message-ID: | CAB=Je-HnDSWsmHLy6U5dsaajv8JBWDDX7mz40vvDBkfE5ToN-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Vladimir> pgjdbc just passes "unknown type" formatted as full timestamp
Vladimir>That backfires for the case "select ?" when backend has no way to
tell what was the "expected bind type"
It might be the case the proper solution is something around
setObject(int parameterIndex, Object x, SQLType targetSqlType)
and
setObject(int parameterIndex, Object x, SQLType targetSqlType,
int scaleOrLength)
Of course, those methods just throw "not implemented", however
setObject(..., SQLType.TIMESTAMP) might be the way.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Raiskup | 2018-04-14 18:27:31 | [pgjdbc/pgjdbc] 6bb72e: packaging: fix RPM build requirements |
| Previous Message | Rémi Aubel | 2018-03-29 13:41:23 | Re: "could not determine data type of parameter" with timestamp |