On Friday 13 May 2005 18:21, Gordon wrote:
If you can add a table structure why not create a SELECTED table with
REPORT ID and PERSON ID as the 2 field PRIMARY KEY.
Then you could INSERT IGNORE into this table [with no BEGN/COMMIT] and the
IGNORE would throw away those already selected.
I have a curious situation I was hoping someone could shed some light on.
mysql select count(*) table;
+---+
| table |
+---+
| 0 |
+---+
1 row in set (0.00 sec)
mysql select count(*) from table;
+--+
| count(*) |
+--+
|25965 |
+--+
1 row in set (0.00
[EMAIL PROTECTED] wrote:
I have a curious situation I was hoping someone could shed some light on.
mysql select count(*) table;
+---+
| table |
+---+
| 0 |
+---+
1 row in set (0.00 sec)
mysql select count(*) from table;
+--+
| count(*) |
+--+
|25965 |
hi,
i followed this thread and really think that this isn't a locking problem, but a
table structure problem.
if there is a column in table with a boolean flag (dealt yes/no) the queries go
just looking for rows where dealt=0 (or no).
Mathias
Selon Duncan Hill [EMAIL PROTECTED]:
On Friday 13
Hi,
with a table with 33 rows, i have the row in 0s using index on term.
mysql select * from tx where term like 'Britney Spears' ;
+++
| id | term |
+++
| 327681 | Britney Spears |
+++
1 row in set (0.00
As it happens, I found this post useful tonight for an almost identical
situation.
I have a table with exactly 200,000 rows, the first column is an
autoincrement ID field. I am confident that all IDs are consecutive and
there are no holes.
When I do:
Select ID from history where id =
