There's a bunch of very ugly code in backend/main/main.c that involves
the preprocessor constants "NOFIXADE" and "NOPRINTADE". The code seems
to be related to support for Alpha and/or ultrix4. NOFIXADE is defined
by port/osf.h and port/ultrix4.h, while NOPRINTADE is not defined as far
as I can tell
Quoth the JDBC spec:
public interface CallableStatement
extends PreparedStatement
The interface used to execute SQL stored procedures. The JDBC API provides a
stored procedure SQL escape syntax that allows stored procedures to be called
in a standard way for all RDBMSs. This escape syntax has one
On Thu, 23 Sep 2004, Grant Finnemore wrote:
> Hi Gavin,
>
> Although I have not read the SQL 2003 spec, my recollection of other database
> products' stored procs differed from your description in one significant way,
> namely that they could return multiple (and varied) sets of rows.
>
> For exam
Hi Gavin,
Although I have not read the SQL 2003 spec, my recollection of other database
products' stored procs differed from your description in one significant way,
namely that they could return multiple (and varied) sets of rows.
For example, a stored proc could do a SELECT over foo and then a SE
Hannu Krosing <[EMAIL PROTECTED]> writes:
> We were bitten by the following bug a few times, when our server tried
> to reestablish connections under bad network conditions:
>
> if connection is closed while trying to get response to SSL setup packet
> (i.e. conn->status is CONNECTION_SSL_STARTUP),
Hi all,
Following is a proposal to implement what SQL2003 calls 'SQL-Invoked
Procedures' and what most people refer to as stored procedures. Fujitsu
will be funding Neil Conway and I to work on this feature.
Procedures
--
Procedures are nearly identical to functions. From my reading of
S
On Wed, 2004-09-22 at 15:29, James William Pye wrote:
> I think so.
Patch applied with some additional fixes -- the patch as I applied it is
attached. Thanks!
-Neil
Index: doc/src/sgml/installation.sgml
===
RCS file: /home/neilc/pri
We were bitten by the following bug a few times, when our server tried
to reestablish connections under bad network conditions:
if connection is closed while trying to get response to SSL setup packet
(i.e. conn->status is CONNECTION_SSL_STARTUP), we get a busy loop, as
line 1035 in 8.0.0.beta2:
On Tue, 2004-09-21 at 23:28, David Fetter wrote:
> Kind people,
>
> I've figured out something that many others probably have, but I
> thought I'd put it out there anyhow.
>
> As PL/PgSQL doesn't allow assignment of singleton SELECTs and dynamic
> queries to variables, as mentioned in the docs.
>
Oleg,
> is this valid for contrib modules ?
Absolutely. Provided the contrib modules are *new* for 8.0.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 8: explain analyze is your friend
Hi all,
I succesfull compiled postgres 8.0beta2 with a recent gcc 4.0 snapshot:
gcc (GCC) 4.0.0 20040911 (experimental)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR
> There have been noises of adding a new catalog for keeping comments for
> shared objects (which would itself be shared, of course). I'm not sure
> what the rationale is for not putting them in the pg_shadow catalog.
Does TOAST work on shared objects?
---(end of broadca
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> There have been noises of adding a new catalog for keeping comments for
> shared objects (which would itself be shared, of course). I'm not sure
> what the rationale is for not putting them in the pg_shadow catalog.
The fact that it wouldn't scale conv
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Wed, Sep 22, 2004 at 03:02:22PM +0200, Laszlo Hornyak wrote:
>> Tom, is there other way in pg 7.4 than backporting PG_TRY? It seems a lot
>> of work.
> IIRC PL/Python had a hack involving sigsetjmp (which was removed in
> favor of the cleaner PG_TRY)
Dear Alvaro,
Thus I would suggest to add one new text field in pg_group and pg_shadow
for this purpose, that could be initialized with something like:
CREATE USER calvin COMMENT 'Calvin <[EMAIL PROTECTED]>';
Alternatively, it could be managed with "COMMENT ON ..."? Well, users or
groups are
On Wed, Sep 22, 2004 at 03:02:22PM +0200, Laszlo Hornyak wrote:
>
> Tom, is there other way in pg 7.4 than backporting PG_TRY? It seems a lot
> of work.
IIRC PL/Python had a hack involving sigsetjmp (which was removed in
favor of the cleaner PG_TRY). You could try doing that.
--
Alvaro Herrera
On Wed, Sep 22, 2004 at 01:15:42PM +0200, Fabien COELHO wrote:
> As I'm managing accounts for students... I noticed that there does not
> seem to be a proper way to keep a comment about a postgresql user account,
> such as the full name of the student or its email, that I could see with
> \du o
Tom, is there other way in pg 7.4 than backporting PG_TRY? It seems a lot
of work.
Thanks,
Laszlo
On Tue, 21 Sep 2004, Tom Lane wrote:
> Laszlo Hornyak <[EMAIL PROTECTED]> writes:
> > I am implementing a java language handler. If unrecoverable error occurs,
> > it needs to send a signal to the
Dear developers,
As I'm managing accounts for students... I noticed that there does not
seem to be a proper way to keep a comment about a postgresql user account,
such as the full name of the student or its email, that I could see with
\du or some system query. My solution is to keep the "mappin
19 matches
Mail list logo
