Ben Grimm <[EMAIL PROTECTED]> writes:
> On Thu, 04 Sep 2003, Tom Lane wrote:
>> Ben Grimm <[EMAIL PROTECTED]> writes:
>>> I haven't tried the 7.4 beta, so it may be fixed there - but in
>>> 7.3.4, pg_dumpall doesn't output global database ACL's.
>>
>> This is fixed for 7.4.
> Is there a patch to
"A.Bhuvaneswaran" <[EMAIL PROTECTED]> writes:
> Should i require to upgrade? or, Is there any smart sql?
If you still see the problem after updating to 7.3.4, it would be worth
investigating further. But given that the symptom looks just like a
known 7.3.2 bug, I don't see any value in spending t
"Marek Lewczuk" <[EMAIL PROTECTED]> writes:
> CREATE FUNCTION "public"."test" (text, text) RETURNS text AS'
> BEGIN
> IF $1 THEN
> RETURN $1;
> ELSE
> RETURN $2;
> END IF;
> END;
> 'LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY INVOKER;
If there's a bug here at all, it's
Hi,
I am using 7.3.2 on redhat linux 7.3.
I am getting this error during update. My update sql is,
test_pg=# update po_header set emp_name = a.user_name from users a where
emp_code = a.user_code and emp_name != a.user_name and a.user_name is not
null;
I referred the link,
http://archives.pos
A message from [EMAIL PROTECTED] to [EMAIL PROTECTED]
entitled Re: Re: My details was virus infected and was not delivered.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmail
Hello,
I think that there is a bug in plPGSQL - or maybe I don't know something
about this language. Try to create this function
Ok., this is the function created in plPGSQL:
CREATE FUNCTION "public"."test" (text, text) RETURNS text AS'
BEGIN
IF $1 THEN
RETURN $1;
ELSE
RETURN $2;
E
