From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'The Hermit Hacker'" <scrappy(at)hub(dot)org>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: query results different in v7.0 vs v6.5.3 ... |
Date: | 2000-05-11 14:24:34 |
Message-ID: | 219F68D65015D011A8E000006F8590C604AF7D7B@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Okay, not sure if this is a bug in v6.5.3 or v7.0, but the same query
> running on the *same* data, but v6.5.3 vs 7.0 ...
>
> SELECT pl.code,p.description,p.price
> FROM po pu,products p, po_list pl
> WHERE pl.po_num = 118
> AND pl.code = p.code
> ORDER BY p.description;
>
>
> produces 2 records (expected) under v6.5.3) but under v7 produces 224
> ... what it appears to do is repeat each of those 2 records 112 times,
> which is the size of the 'po' table ...
>
> Since we aren't actually *using* the 'po' table in that
> query, I removed
> it in the v7.0 system and it comes back with the two records
> I'm expecting
> ...
>
> So, my first guess is that v6.5.3 was less strict as far as
> tables listed
> in the FROM directive then v7.0, so it just ignored it if it wasn't
> actually used ... but want to make sure it *isn't* a bug
> we've introduced
> with v7.0 ...
No, was a bug in 6.5
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-11 14:47:06 | Re: Now 376175 lines of code |
Previous Message | Michael Robinson | 2000-05-11 14:06:50 | Re: Multibyte still broken |