Thread

1. changed SQL in 6.4?

   Sascha Schumann <sas@schell.de> — 1998-11-30T23:00:44Z

   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
   
   
   

2. Re: [SQL] changed SQL in 6.4?

   pierre@desertmoon.com — 1998-12-01T01:22:47Z

   > 
   > 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
   > 
   > 
   >