Re: Storing timestamps in text format
| От | Dave Cramer |
|---|---|
| Тема | Re: Storing timestamps in text format |
| Дата | |
| Msg-id | AANLkTimmW20LLj_aWRv+bLOW=c8wok48zYKOR0KPAWqL@mail.gmail.com обсуждение исходный текст |
| Ответ на | Storing timestamps in text format (Radosław Smogura <rsmogura@softperience.eu>) |
| Ответы |
Re: Storing timestamps in text format
|
| Список | pgsql-jdbc |
On Fri, Nov 26, 2010 at 1:28 PM, Radosław Smogura
<rsmogura@softperience.eu> wrote:
> Hi,
>
> I perform following test:
> 1. Open connection (GMT+1)
> 2. Change timezone (GMT+3)
> 3. Write created timestamp.
> 4. Change timezone to different connection open and write (GMT+4)
> 5. Read timezone
>
> During this I saw driver sends timestamp encoded with initial (in my case
> +1), form connection open, time zone. It's because
> TimestampUtils.toString(Calendar, Timestamp) uses defaultCal. Should it use
> Calendar.getInstance() or new GregorianCalendar?
>
> public synchronized String toString(Calendar cal, Timestamp x) {
> if (cal == null)
> cal = defaultCal; // = Calendar.getInstance() // new
> GregorianCalendar()
>
What do you expect it to do?
>
> --
> ----------
> Radosław Smogura
> http://www.softperience.eu
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
В списке pgsql-jdbc по дате отправления: