gnue-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnue-dev] problems with new parser, too


From: Holger Schurig
Subject: [Gnue-dev] problems with new parser, too
Date: Sun, 6 Jan 2002 21:27:26 +0100

So I thought the old parser is buggy and commented out the call to this 
parser:


/* note: server side classes must be first, so can be inherited from */
// message ("Load business class definitions (old parser)");
// load_class_files ();

message ("Load business class definitions (new parser)");
init_classdef ();

Now it worked better. It still shows strange errors ...

Load business class definitions (new parser)
addrbook.gcd:7: no format allowed for this type
    text name<20>;
                ^
addrbook.gcd:16: no format allowed for this type
    text description<16>;
                       ^
addrbook.gcd:17: no format allowed for this type
    text value<16>;
                 ^
addrbook.gcd:18: unknown type 'object'
    object person;
           ^
addrbook.gcd:26: unknown type 'lookup'
    lookup country : addressbook::country(id).name = countrycode;
           ^

However, it continued afterwards. But it produced bad SQL statements. 
Later on it said:

[create table geas__user (sys_id char(32) , sys_cre_user varchar(16) , 
sys_cre_time datetime , sys_mod_user varchar(16) , sys_mod_time 
datetime , username varchar(32) , password varchar(32) , 
_currenttransaction char(32) , primary key (sys_id) )] succeeded
error: [postgresql.c/878] [postgresql_update_tables] [create table 
geas__searchfield (sys_id char(32) , sys_cre_user varchar(16) , 
sys_cre_time datetime , sys_mod_user varchar(16) , sys_mod_time 
datetime , invert bool , casesensitive bool , test int2 , field 
varchar(128) , value varchar(128) , constraint char(32) , primary key 
(sys_id) )] failed error: [postgresql.c/879] [postgresql_update_tables] 
ERROR:  parser: parse error at or near "char"

I copied the SQL statement and fed it peace by peace into PostgreSQL 
(7.1.3-5 from Debian). It turned out that PostgreSQL doesn't like a 
field with the name "constraint". Constraint is actually named in 
postgresql.reserved.lst.

Another statement that didn't made it was

error: [postgresql.c/878] [postgresql_update_tables] [create table 
geas__listitem (sys_id char(32) , sys_cre_user varchar(16) , 
sys_cre_time datetime , sys_mod_user varchar(16) , sys_mod_time 
datetime , position int2 , listid char(32) , reference char(32) , 
primary key (sys_id) )] failed
error: [postgresql.c/879] [postgresql_update_tables] ERROR:  parser: 
parse error at or near "position"


Greetings,
Holger



reply via email to

[Prev in Thread] Current Thread [Next in Thread]