[SQL] PARSER ERROR persists ....

2001-09-27 Thread Frederick Klauschen 

Hi,

I have tried Carl's suggestion, but it does
not make a difference and the same
ERROR: parser: parse error at or near (
results.
I have rebuilt and reinstalled Version 7.1.3,
but still the same. No compilation or installation
errors are reported and simple statements seem
to work properly. In contrast to 7.0.3, the \d table
command does not work because 'format_type(oid,int4)'
does not exist, but this 
probably has nothing to do with my problem?
I am running SuSE Linux 7.2 (kernel 2.4.4).
Might any libraries not be loaded or could there
be any other problem related to installation?

Thanks, Frederick


Here is Josh's statement with Carl's modification:

SELECT people.people_id, people.name,
   people.address,
   people_attributes.attribute_name,   
   people_attributes.attribute_value
FROM people, people_attributes,
   ( SELECT people_id, count(*) as match_count
 FROM people_attributes, search_attributes 
 WHERE search_id = 31
 AND people_attributes.attribute_name = 
 search_attributes.attribute_name
 AND people_attributes.attribute_value ~* 
 search_attributes.attribute_value
 GROUP BY people_id) matches,
   ( SELECT count(*) as attribute_count
 FROM search_attributes
 WHERE search_id = 31 ) searched
WHERE people.people_id = people_attributes.people_id
  AND people.people_id = matches.people_id
  AND matches.match_count = searched.attribute_count;



__
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [SQL] PARSER ERROR persists ....

2001-09-27 Thread Tom Lane 

Frederick Klauschen [EMAIL PROTECTED] writes:
 I have rebuilt and reinstalled Version 7.1.3,
 but still the same. No compilation or installation
 errors are reported and simple statements seem
 to work properly. In contrast to 7.0.3, the \d table
 command does not work because 'format_type(oid,int4)'
 does not exist, but this 
 probably has nothing to do with my problem?

Actually, that's a red flag indicating that you did the wrong thing.
You may be running a 7.1.3 psql, but the server you are talking to
is not 7.1.*, but something older (try select version() to prove it).

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

[SQL] PARSER ERROR

2001-09-26 Thread Frederick Klauschen 

The commas did not get cut off and I think I 
did not make any other mistakes either.
Is it also possible that the parser does not work
properly?

Thanks, Frederick

Here is what happened again:

ERROR: parser: parse error at or near ( 
when running :

 SELECT people.people_id, people.name,
people.address,
people_attributes.attribute_name,   
people_attributes.attribute_value
 FROM people, people_attributes,
( SELECT people_id, count(*) as match_count
  FROM people_attributes, search_attributes 
  WHERE search_id = 31
  AND people_attributes.attribute_name = 
  search_attributes.attribute_name
  AND people_attributes.attribute_value ~* 
  search_attributes.attribute_value )
 matches,
( SELECT count(*) as attribute_count
FROM search_attributes
  WHERE search_id = 31 ) searched
 WHERE people.people_id = people_attributes.people_id
   AND people.people_id = matches.people_id
   AND matches.match_count =
 searched.attribute_count;

Postgresql Verson 7.0.3 and 7.1.3.

__
Do You Yahoo!?
Get email alerts  NEW webcam video instant messaging with Yahoo! Messenger. 
http://im.yahoo.com

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html