[EMAIL PROTECTED] writes:
> After I installed the new RedHat 7.3 with Postgres 7.2 some of my
> SQLs didn't worked. Mainly thoose, with the timestamp function:
> timestamp(current_date, current_time)
> does work under 7.1 but under 7.2 there is an parser error!
You're gonna have to rename the f
> timestamp(current_date, current_time)
> does work under 7.1 but under 7.2 there is an parser error!
Please check the release notes and the SQL standard for why you can not
call a function timestamp() directly; the syntax is now reserved for
specifying a data type, not a function call.
For th
Juan Salazar
Administrador de Red
Planok S.A.
Fono : +56 2 2364119
Mail : [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
[EMAIL PROTECTED] writes:
> function datetime() and extract() returns wrong timezone offset values. This is
>present in v7.2.1 but NOT in v7.0.3:
> template1=# select datetime(1024903424) \g
> timestamp
> -
> 2002-06-23 22:23:44
> (1 row)
This part is not a bug
Hello,
I am trying to set up my database by entering the following command:
"initdb -D /Users/Shared/PostgreSQL/data"
I get the following message from the shell: "initdb Unknown command"
Any Ideas for troubleshooting this problem?
Thanks,
Tom Castonzo
---(end of bro
Sandor, Vig ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
timestamp function does not work?
Long Description
I've wrote an application under PHP, wich uses Postgres 7.1.
After I installed the new RedHat 7.3 with Postgres 7.2
Tom Lane writes:
> You seem to have missed the point completely - Neil wanted to suppress
> the normal progress messages *on stderr* so that he'd only get an email
> report when there was an abnormal event. That request seemed fine to
> me, though I thought the patch itself might have some porta
N. Fung ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Wrong Timezone offset (like bug#672)
Long Description
function datetime() and extract() returns wrong timezone offset values. This is
present in v7.2.1 but NOT in v7.0.3
Hi all,
I has some disappointed, when read that PG can't
return OID of statements, which had INSERTed multiple
rows (not "exactly one"). Please help, how can I know
OID of last(or first) inseted row ?
Thanks for your suggestions.
Ruslan A Dautkhanov [EMAIL PROTECTE
Patch applied. Thanks.
---
Dmitry Tkach wrote:
> Ok, this sit around for a while, and, because there was no responses, I assume, that
>nothing jumps out
> at you as being terribly with my logic...
> Here is the patch (se
10 matches
Mail list logo
