From: "Andreas Pflug" <[EMAIL PROTECTED]>
> Hiroshi Saito wrote:
>
> >I am sleepy fo JST time.:-)
> >
> Can't understand that, 22:30 is best working time!
>
Oh.
I must seem to fight against the iron person.
I go to buy "time" in the department store.:-)
Regards,
Hiroshi Saito
---
Hiroshi Saito wrote:
I am sleepy fo JST time.:-)
Can't understand that, 22:30 is best working time!
Regards,
Andreas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
From: "Andreas Pflug" <[EMAIL PROTECTED]>
> Dave Page wrote:
(snip)
> >We've had no complaints about keywords causing problems anywhere (in
> >pga2 or pga3), and the aggregate problem is obviously a real one - I
> >vote we go with Hiroshi's patch for now, and take a closer look for the
> >next ver
Dave Page wrote:
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 09 September 2003 13:55
To: Dave Page
Cc: Hiroshi Saito; [EMAIL PROTECTED]
Subject: Re: [pgadmin-hackers] pgAggregate problem any function
Dave Page wrote:
I guess we should really check
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 09 September 2003 13:55
> To: Dave Page
> Cc: Hiroshi Saito; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] pgAggregate problem any function
>
>
> Dave Page wrote:
>
> &g
Dave Page wrote:
I guess we should really check them all. Can we jsut lift the relevant
bits of
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/pars
er/keywords.c?rev=1.141&content-type=text/x-cvsweb-markup, or would you
prefer it was done a different way?
I just added this to
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 09 September 2003 12:16
> To: Dave Page
> Cc: Hiroshi Saito; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] pgAggregate problem any function
>
>
> Didn't want to check
Dave Page wrote:
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 09 September 2003 11:50
To: Dave Page
Cc: Hiroshi Saito; [EMAIL PROTECTED]
Subject: Re: [pgadmin-hackers] pgAggregate problem any function
Hm,
looking at the patch and the weird pgsql behaviour
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 09 September 2003 11:50
> To: Dave Page
> Cc: Hiroshi Saito; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] pgAggregate problem any function
>
>
> Hm,
>
> looking
Hm,
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 tha
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=#
12 matches
Mail list logo
