From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Vinayak <vinpokale(at)gmail(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Problem with DATE |
Date: | 2015-01-13 11:45:56 |
Message-ID: | CADK3HHKogHhRauJ9w9Dr=H_qinbaZcc6v6ZLXYnAuaxLmLz0xg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
No there is no similar problem for Date as there is only one date type in
postgresql. If all you need is date then you should able to use that
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On 13 January 2015 at 01:42, Vinayak <vinpokale(at)gmail(dot)com> wrote:
> Hi,
>
> I have checked the below description in one post:
> If the timestamp parameter is given, the jdbc does not know if it is to be
> used timestamp or timestamptz. The jdbc driver passes it to the server as
> an
> unknown data type letting the server figure out what to do with it.
> Example:
> timestampcol = ? or if you're inserting into a timestamp field so the
> server
> can determine the datatype of parameter being used at, in this case since
> its just being sent back to the user the server cannot determine the data
> type.
> so we need to typecast it.
> "SELECT ?::timestamp"
>
> Is the same problem for date type also?
>
>
>
>
> -----
> Regards,
> Vinayak,
>
> --
> View this message in context:
> http://postgresql.nabble.com/Problem-with-DATE-tp5833008p5833708.html
> Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | Lachezar Dobrev | 2015-01-13 15:28:15 | Re: Problem with DATE |
Previous Message | Vinayak | 2015-01-13 06:42:54 | Re: Problem with DATE |