From: | elein <elein(at)norcov(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Cc: | elein <elein(at)norcov(dot)com> |
Subject: | plpython plpy.log/warning minor aesthetic bug |
Date: | 2002-09-22 00:35:21 |
Message-ID: | 200209220034.g8M0YvBd679814@pimout1-ext.prodigy.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Postgres7.3b1, Linux Suse 7.3
plpy.log() and plpy.warning() leave parentheses and a trailing
comma on messages in psql and in the log. I did not test
the other plpy interfaces to elog. This is what they look like:
WARNING: ('This is a warning!',)
LOG: ('This is a log message.',)
The parens are OK, but the trailing comma bothers my
brain parser.
------warnme.sql----
drop function warnme():
create function warnme()
returns text as
'
plpy.warning( "This is a warning!" )
return "warning"
' LANGUAGE 'plpython';
drop function logme();
create function logme()
returns text as
'
plpy.log( "This is a log message." )
return "log message"
' LANGUAGE 'plpython';
select warnme();
select logme();
--
-- Log file results:
--
-- WARNING: ('This is a warning!',)
-- LOG: ('This is a log message.',)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-22 00:44:01 | Re: No dependency between fkey constraint and unique index |
Previous Message | Tom Lane | 2002-09-21 00:40:39 | Re: Server hangs on multiple connections |