looking at the patch and the weird pgsql behaviour documented below I doubt that this is the ultimate fix.
I suspect that
a) this should be handled in qtIdent()
b) other keywords might be affected, e.g. 'char'
Regards, Andreas
Dave Page wrote:
Thanks Hiroshi, patch applied (I ran into that problem in pga2!)
Regards, Dave.
-----Original Message-----
From: Hiroshi Saito [mailto:[EMAIL PROTECTED] Sent: 09 September 2003 06:17
To: Andreas Pflug
Cc: [EMAIL PROTECTED]; Dave Page
Subject: pgAggregate problem any function
Hi Andreas.
There is a problem by handling of any of the input type.
This patch will just be able to do it. any -> "any"
But, Is it likely to be the problem of parser of postgresql? "ANY" is written in the document. But, drop isn't made though "ANY" can be registered.
This is with psql. saito=# DROP AGGREGATE public.newcnt(any); ERROR: syntax error at or near "any" at character 30 saito=# DROP AGGREGATE public.newcnt(ANY); ERROR: syntax error at or near "ANY" at character 30 saito=# DROP AGGREGATE public.newcnt("ANY"); ERROR: type "ANY" does not exist saito=# DROP AGGREGATE public.newcnt("any"); DROP AGGREGATE
Any Comment?
Regards, Hiroshi Saito
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
