Thread: changed SQL in 6.4?

changed SQL in 6.4?

From
Sascha Schumann
Date:
Hi list,

I've dumped my databases, but 6.4 doesn't like the code produced by
6.3.2's pg_dump.

CREATE TABLE user (username varchar(128), realname varchar(128), password
varchar(128), allow int4, id int4);
ERROR:  parser: parse error at or near "user"

Exact the same statement works perfectly with 6.3.2. It also doesn't like
INSERTing in tables named user. Is user a reserved name?

          Regards,

                            Sascha Schumann |
                                 Consultant | finger sas@schell.de
                                            | for PGP public key


Re: [SQL] changed SQL in 6.4?

From
pierre@desertmoon.com
Date:
>
> Hi list,
>
> I've dumped my databases, but 6.4 doesn't like the code produced by
> 6.3.2's pg_dump.
>
> CREATE TABLE user (username varchar(128), realname varchar(128), password
> varchar(128), allow int4, id int4);
> ERROR:  parser: parse error at or near "user"
>
I found the same thing in my conversion process. The keyword user is
reserved....change your table name to users and it will work, however
you'll need to change all references to the table user to users
as well.

-=pierre

> Exact the same statement works perfectly with 6.3.2. It also doesn't like
> INSERTing in tables named user. Is user a reserved name?
>
>           Regards,
>
>                             Sascha Schumann |
>                                  Consultant | finger sas@schell.de
>                                             | for PGP public key
>
>
>