. Is that
supposed to be that way? Is it likely to change?
Thanks,
Kev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On the 2009-01-01 win32 release, I noticed I could no longer debug,
like when I'd set a breakpoint I'd immediately get the error message:
syntax error at or near ,
LINE 1: SELECT * FROM pldbg_set_global_breakpoint(, 55208, NULL,
NUL...
...and the output pane of the debugger would show:
row
On Mar 13, 9:30 am, dp...@pgadmin.org (Dave Page) wrote:
On Fri, Mar 13, 2009 at 1:19 PM, Kev kevinjamesfi...@gmail.com wrote:
On the 2009-01-01 win32 release, I noticed I could no longer debug,
Temporary bug that's since been resolved. Sorry 'bout that.
Oh, no worries, thanks for the reply
the variables to configure exceptions and
special features, especially when using mod_libpq or otherwise trying
to minimize the code that exists outside the database server.
What do you think?
Thanks,
Kev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Apr 8, 10:40 am, [EMAIL PROTECTED] (Gregory Stark) wrote:
Kev [EMAIL PROTECTED] writes:
Would it be a lot of trouble to extend the ability that databases have
to store variables (add_missing_from, array_nulls, etc.) to tables and
columns, for use with user-defined variables
