Kris Jurka <[EMAIL PROTECTED]> writes:
> [ GEQO doesn't work anymore in CVS tip ]
Ugh. The proximate cause of this is the code I added recently to cache
repeated calculations of the best inner indexscan for a given inner
relation with potential outer relations. Since geqo_eval() releases
all mem
On Fri, 6 Dec 2002 [EMAIL PROTECTED] wrote:
> Sample Code
> SELECT * FROM tbluser WHERE userid = ""
I assume you mean '' rather than "".
0 length strings used to be interpreted as having
the value 0 when converted into an integer. Now it
throws an error instead. There was some discussion
at t
Stéphane Bérubé ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Query with null string
Long Description
When I do a query (SELECT or INSERT) with null vars (see example) I get warnings from
php:
Warning: pg_query() query faile
On Fri, 6 Dec 2002, Marques Johansson wrote:
> See the ERROR and comments below...
>
> create table photos (
> filename varchar[128] not null,
> filesize int default null,
> width int default null,
> height int default null,
> origPhoto oid default null references photos ( oid ),
> alt
Hello Marques,
Your problem is that the oid is not indexed.
Create an index on photos(oid) then add the constraint separately.
JLL
Marques Johansson wrote:
>
> See the ERROR and comments below...
>
> create table photos (
> filename varchar[128] not null,
> filesize int default null,
>
See the ERROR and comments below...
create table photos (
filename varchar[128] not null,
filesize int default null,
width int default null,
height int default null,
origPhoto oid default null references photos ( oid ),
altDesc varchar[128] default null
);
psql:sid-sql:40: NOTICE: CR
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Ah, thanks for the simplified test case. This is undoubtedly my fault
>> ... will look into it. It is probably somewhat related to the join
>> alias problem found yesterday (ie, somebody somewhere is trying to use
>> the wrong rangetable
Tom Lane wrote:
Ah, thanks for the simplified test case. This is undoubtedly my fault
... will look into it. It is probably somewhat related to the join
alias problem found yesterday (ie, somebody somewhere is trying to use
the wrong rangetable list to interpret a Var node).
I spent a bit more
Joe Conway <[EMAIL PROTECTED]> writes:
> I can confirm this both on cvs tip (pulled after noon PST today) and 7.3
> stable branch. It is not related to dblink, but rather the backend. Here's a
> (contrived) script based on Kris's example to trigger it:
Ah, thanks for the simplified test case. T
