Stephan Szabo <[EMAIL PROTECTED]> writes:
> On Tue, 2 Apr 2002, Tom Lane wrote:
>> Hm ... isn't it NULL anyway, if the left side is NULL?
> I think the empty case is special, due to the rules on comparison predicate>s.
[ reads spec... ] Yeah, I think you are right.
Looks like our subplan impl
"Vlad Marchenko" <[EMAIL PROTECTED]> writes:
> test=# select count(*) from subscribers;
> count
> ---
> 96856
> (1 row)
> test=# select * from subscribers where email~'domain4';
> sid | email | domain | status | password | signup | name | sex | address |
> city | state | zip | country | ph
Joe Piscitella <[EMAIL PROTECTED]> writes:
> checking test program... failed
> configure: error:
> *** Could not execute a simple test program. This may be a problem
> *** related to locating shared libraries. Check the file 'config.log'
> *** for the exact reason.
The usual cause of this is t
On Tue, 2 Apr 2002, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Are the array iterator functions supposed to act sort of like
> > =ANY/=ALL except across an array instead of a subselect?
>
> Seems like a reasonable definition.
>
> > If so,
> > isStrict probably isn't right, si
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Are the array iterator functions supposed to act sort of like
> =ANY/=ALL except across an array instead of a subselect?
Seems like a reasonable definition.
> If so,
> isStrict probably isn't right, since for an empty subselect the return
> value does
On Tue, 2 Apr 2002, Tom Lane wrote:
> Matt Peterson <[EMAIL PROTECTED]> writes:
>
> > + if(value == 0)
> > + {
> > + /* elog(NOTICE, "array_iterator: value is null"); */
> > + return (0);
> > + }
>
> This patch is certainly wrong, as it will break array_iterator
hello
i've got the following error:
here is the output:
###
osk=> select age('2001-03-29','2001-03-01');
age
---
27 days 23:00
(1 row)
osk=> select age('2002-03-29','2002-03-01');
age
---
1 mon
(1 row
Inserting text with an apostrophe fails. Updating a record after it's
initial creation works fine.
PGAccess version: 0.98.7 (as included with Mandrake 8.2).
file: pgaccess/lib/tables.tcl
fixed lines: 547-548...
546: lappend PgAcVar(mw,$wn,newrec_fields) "\"$fld\""
547: regsub -all {'} $fldva
I have a pg_dump file which contains only schemas,
I think there is a bug, which causes function reload
fail, look at following pieces of dump file:
..
..
--
-- TOC Entry ID 212 (OID 34744710)
--
-- Name: gibson Type: TABLE Owner: jliang
--
CREATE TABLE "gibson" (
"cid" integer,
Matt Peterson <[EMAIL PROTECTED]> writes:
> + if(value == 0)
> + {
> + /* elog(NOTICE, "array_iterator: value is null"); */
> + return (0);
> + }
This patch is certainly wrong, as it will break array_iterator for
non-pointer datatypes (no, I do not believe your
Good day. Please reveiew log below.
test=# \d subscribers;
Table "subscribers"
Column | Type | Modifiers
--++
---
sid | bigint
Ops.. I've got it, disregard my email - random() generates duplicate values
on 10 long sequence
:-)
sorry.
--
Best Regards,
Vlad Marchenko
- Original Message -
From: "Vlad Marchenko" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 29, 2002 2:18 PM
Subject: huh!?
I have added the following packages:
drwxr-xr-x 4 root other512 Apr 1 14:29 SMCflex
drwxr-xr-x 4 root other512 Apr 1 14:29 SMCgtext
drwxr-xr-x 4 root other512 Apr 1 14:28 SMCmake
drwxr-xr-x 4 root other512 Apr 1 14:28 SMCbison
drwxr-xr-x
Hi,
I have been looking at the functions in array_iterator.so. So far they have
proved to be very useful. However, I have manage to find a very serious bug
where the array_iterator() function causes some very bad stack corruption.
The stack corruption appears to be caused because pointer da
14 matches
Mail list logo