Re: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

From: Kris Jurka <books(at)ejurka(dot)com>
To: Farid Zidan <farid(at)zidsoft(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail
Date: 2010-06-05 01:42:20
Message-ID: alpine.BSO.2.00.1006042140040.6416@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 4 Jun 2010, Farid Zidan wrote:

> Here is actual statements I am running and like I said they work for all 9+
> DBMSs (I use ODBC and{fn user()} is the ODBC cross-dbms syntax for the
> current user ID):
>
> '2010-04-30 00:00:00',
> '2010-04-30 00:00:00',
> {fn user() }
>

If you're into using standard ODBC escapes for portability, shouldn't you
be using {ts '2010-04-30 00:00:00'}?

http://msdn.microsoft.com/en-us/library/ms712360%28VS.85%29.aspx

Kris Jurka

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Stark 2010-06-05 02:41:32 Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail
Previous Message Farid Zidan 2010-06-04 22:15:09 Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail