On 11/23/05, David Fetter <[EMAIL PROTECTED]> wrote:
> Having blank lines in -f scripts was causing silent failures. This
> fixes it, for some value of "fixes." If it's OK, please apply to 8.1
> CURRENT and CVS TIP :)
> if (strncmp(buf, "\n", 1) != 0) {
> commands = process_commands(buf);
>
"Yoshihisa Nakano" <[EMAIL PROTECTED]> writes:
> => INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
> INFO: EXECQ: 0
> INSERT 167713 1
> I tried this example, but INFO showed 1, not 0.
Yeah ... the INSERT won't show an OID by default anymore, either.
Fixed; thanks for the report!
"Evan Carroll" <[EMAIL PROTECTED]> writes:
> IE Here is the exact querry
> select fkey_event as F, fkey_event from event_contact UNION select * from
> event_object ORDER BY fkey_event;
> and here is the header from the outputted table
>f | fkey_event
> -+
And? I don't see a
> > A trigger in plpythonu cannot use the `args' list to obtain the
> > arguments and does not return the row to be written into the
> > database. Instead the arguments are placed into a global
> > dictionary called "TD". The row is in TD["new"] as a dictionary
> > keyed by the names of the fields
The following bug has been logged online:
Bug reference: 2096
Logged by: Yoshihisa Nakano
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: RedHat Enterprise Linux ES 3.0
Description:bug in a SPI sample document
Details:
There is a differe
The following bug has been logged online:
Bug reference: 2097
Logged by: Evan Carroll
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Linux -- Debian & Ubuntu.
Description:Union bug.
Details:
There apears to be a bug with the Union feature
