Re: BUG #6391: insert does not insert correct value
От | Kevin Grittner |
---|---|
Тема | Re: BUG #6391: insert does not insert correct value |
Дата | |
Msg-id | 4F0D664E02000025000446AA@gw.wicourts.gov обсуждение исходный текст |
Ответ на | BUG #6391: insert does not insert correct value (john.udick@zionsbancorp.com) |
Ответы |
Re: BUG #6391: insert does not insert correct value
|
Список | pgsql-bugs |
John Udick <John.Udick@zionsbancorp.com> wrote: > We did notice that although now() failed, changing this to > 'now()'::date works (using single quotes around now()). That seem unrelated to the now() function. Casting a literal to a date/time/timestamp supports parsing out certain keywords, like 'now', 'today', 'yesterday', and 'tomorrow'. It's probably ignoring those parentheses. > Also, apparently we are not truly a Postgres database, but EMC's > Greenplum database. I will be working with our admins and EMC, > unless someone in Postgres can point out a specific version that > resolved this issue. > "PostgreSQL 8.2.15 (Greenplum Database 4.1.1.5 build 1) on > x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled > on Sep 20 2011 11:09:08" Yeah, I don't know how much the community lists can help with that implementation. It seems there is a bug in that version, but it might not be present in the community version. -Kevin
В списке pgsql-bugs по дате отправления: