Hello list,
I've found this strange select bug in retrieving rows from a table. I
can best illustrate this with an output of two queries:
mysql select id,jn from paper_2001 limit 10;
+--+---+
| id | jn|
+--+---+
| 19360350 | 6165 |
| 19360351 | 6165 |
|
Renald Buter wrote:
Odd, eh? But what's worse, the JOIN between this column and other
columns *also* uses this truncated values and the result is bogus.
I wouldn't say odd, as you didn't specified any order I wouldn't rely on
the order of the output. Try ordering things for what you want and
On 11:34 Thu 31 Aug , Renato Golin wrote:
Renald Buter wrote:
Odd, eh? But what's worse, the JOIN between this column and other
columns *also* uses this truncated values and the result is bogus.
I wouldn't say odd, as you didn't specified any order I wouldn't rely on
the order of the
On Thursday 31 August 2006 12:21, Renald Buter wrote:
The problem is that a simple 1-table query shows different answers
depending on whether you select 1 or 2 columns.
Relational databases are founded on mathematical set theory. Unless you
specify an ORDER BY stanza in your query, the
On 12:27 Thu 31 Aug , Duncan Hill wrote:
On Thursday 31 August 2006 12:21, Renald Buter wrote:
The problem is that a simple 1-table query shows different answers
depending on whether you select 1 or 2 columns.
*blush*
Of course. I see. How stupid.
Thanks and sorry to have bothered
In the last episode (Aug 31), Renald Buter said:
On 12:27 Thu 31 Aug , Duncan Hill wrote:
On Thursday 31 August 2006 12:21, Renald Buter wrote:
The problem is that a simple 1-table query shows different
answers depending on whether you select 1 or 2 columns.
*blush*
Of course. I
