In message <[EMAIL PROTECTED]>, "Oliver Elphick" write
s:
>John Gotts wrote:
> >We're experiencing a problem with the parser with both 6.5.3 and 7.0.2.
> >ERROR: parser: parse error at or near "position"
> >fmfts=# insert into contact_people (user_id,name,"position",email_address)
>v
>
John Gotts wrote:
>We're experiencing a problem with the parser with both 6.5.3 and 7.0.2.
>ERROR: parser: parse error at or near "position"
>fmfts=# insert into contact_people (user_id,name,"position",email_address) v
>alues ('jgotts','hello',null,null);
>INSERT 20402 1
>
>Th
In message <[EMAIL PROTECTED]>, "Robert J. Spr
awls" writes:
>On Sun, 25 Jun 2000, John Gotts wrote:
>JG>We're experiencing a problem with the parser with both 6.5.3 and 7.0.2.
>JG>The following is with 7.0.2. 6.5.3 is similar.
>JG>umpire(rc3.d)% psql -u fmfts
>JG>psql: Warning: The -u option
We're experiencing a problem with the parser with both 6.5.3 and 7.0.2.
The following is with 7.0.2. 6.5.3 is similar.
umpire(rc3.d)% psql -u fmfts
psql: Warning: The -u option is deprecated. Use -U.
...
fmfts=# CREATE TABLE "contact_people" (
fmfts(#"user_id" character(30),
fmfts(# "acco
I am pretty much self taught using SQL, and I suspect that my problem
here is trying to do something silly. I have since changed my tables
and avoided the problem, but I am curious as to why this happens, and
it's remotely possible I have even found a bug or two.
I created a table with only a se
