> I tried to use function date_part('quarter', date) in query and I have
> got wrong results - for first quarter I've got all rows from 01.01 to
> 31.03
> for second - from from 01.04 to 31.07 (!!!)
> for third - from from 01.08 to 30.11 (!!!)
> for forth - from from 01.12 to 31.12 (!!!)
>
"Robert B. Easter" <[EMAIL PROTECTED]> writes:
> Is this a pg_dump bug or is there there some way to do this right?
It's a pg_dump bug --- pg_dump knows how to quote special characters
in string literals, but failed to do so for function bodies
(and a number of other places too). I've committed
Bruno LEVEQUE <[EMAIL PROTECTED]> wrote:
> [ via libpgtcl, the given query updates no rows ]
> If I update directly
> set datestyle to 'postgres, european'; update cheque set ok='x' where num_cpte=8 and
>date='09-11-2000' and nb_cheq=4919351 and lib like 'gynéco' and ok='' and deb=200.00
>and cr
[EMAIL PROTECTED] writes:
> impossible to create a table having the same name of a sequence object
This is not a bug. A sequence is a table, of a sort, and so there's
just one namespace for both.
regards, tom lane
> I tried to use function date_part('quarter', date) in query and I have
> got wrong results...
Yeesh! Don't know what I was thinking at the time, but it sure is wrong.
If you have PostgreSQL built from source, then you can fix this by
editing src/backend/utils/timestamp.c on or around line 2056.
jose ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
impossible to create a table having the same name of a sequence object
Long Description
prova=# \d
List of relations
Name | Type | Owner
--
Hello,
I tried to use function date_part('quarter', date) in query and I have
got wrong results - for first quarter I've got all rows from 01.01 to
31.03
for second - from from 01.04 to 31.07 (!!!)
for third - from from 01.08 to 30.11 (!!!)
for forth - from from 01.12 to 31.12 (!!!)
