> since a few hours I try to set-up Latin-2 sort order in PostgreSQL 7.1.3. I
> have re-compiled it with MB and Latin2, I have re-initialized database, I
> have restored dumps, which contained "ENCODING='LATIN2'" in it ... and it's
> still nothing.
You need to enable locale support. MB support do
Hello,
since a few hours I try to set-up Latin-2 sort order in PostgreSQL 7.1.3. I
have re-compiled it with MB and Latin2, I have re-initialized database, I
have restored dumps, which contained "ENCODING='LATIN2'" in it ... and it's
still nothing.
Could anyone send me a step-by-step instruction
Jari Aalto writes:
> class=# \i pg-def-group-grant.sql
> Granting ALL to ROOT
> CHANGE
> Granting ALL to USER
> psql:pg-def-group-grant.sql:48: ERROR: parser: parse error at or near "user"
You need to double quote "user". It's a reserved word.
> Granting SELECT to READER
> psql:pg-def-group-g
Jari Aalto wrote:
>
>Can anyone suggest, what is wrong with the following
>sql file? SOmehow the semicolon causes error?
...
>Granting ALL to USER
>psql:pg-def-group-grant.sql:48: ERROR: parser: parse error at or near "user
>"
...
>32:GRANT ALL ON
>33: bonus
>34: ,
Can anyone suggest, what is wrong with the following
sql file? SOmehow the semicolon causes error?
Jari
class=# \i pg-def-group-grant.sql
Granting ALL to ROOT
CHANGE
Granting ALL to USER
psql:pg-def-group-grant.sql:48: ERROR: parser: parse error at or near "user"
Granting SELECT t
It looks like it works here :(. Do you have an error
message?
processdata=# select version();
version
---
PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by
GCC 2.95.4
(1 row)
pr
On Wed, 22 Aug 2001, Jayson Callaway wrote:
> In postgres 7.0.x I had some working code that lookes something like:
>
> CREATE TABLE category
> (
> uid int4 PRIMARY KEY,
> description text NOT NULL,
> parent int4 NULL REFERENCES category(uid)
> )
>
> After upgrading to postgres 7.1.
In postgres 7.0.x I had some working code that lookes something like:
CREATE TABLE category
(
uid int4 PRIMARY KEY,
description text NOT NULL,
parent int4 NULL REFERENCES category(uid)
)
After upgrading to postgres 7.1.2 however this syntax is not accepted
anymore. I receive an error
Mark,
The responses to your problem are gonna be kinda slow, as 2/3 of the
core team, and many of the users, are at the Expo right now (and if
anyone on the list is in the SF Bay Area, join us! BOF session
tonight!)
> we need to control database changes within BEFORE triggers.
> There is no pro
hi,
Idon't know the best way but how about a quick insert in a temp table and
adding 1 to the inserted oid column each time the trigger will run.!
regards
Omid
>From: Markus Wagner <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED], [EMAIL PROTECTED],
>[EMAIL PROTECTED]
>Subject: [SQL] getting the oid
hi,
Grant all on sequence_name to theuser ;
regards
omid
>From: "Vladimir Terziev" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: [SQL]
>Date: Wed, 29 Aug 2001 10:40:00 +0300
>
>Hi,
>
>I'm writing a script, which has to retrieve a next value from a sequnce. I
>use
>mod_perl, DBI and DBD::
Hi,
we need to control database changes within BEFORE triggers.
There is no problem with triggers called by update, but there is
a problem with triggers called by insert.
We strongly need to know the oid of a newly inserted tuple. In this case, we
use tg_newtuple of the TriggerData structure pa
Hi,
I'm writing a script, which has to retrieve a next value from a sequnce. I use
mod_perl, DBI and DBD::Pg version 0.98.
I notice that when I execute "select nextval('sequence_name'::text) AS
sname;", via DBI, the value of sequence is updated, but the mod_perl returns
"DBD::Pg::st execute f
13 matches
Mail list logo
