Before I start, I know that HANDLER (ie, HANDLER table OPEN, HANDLER table
READ, etc) are low level and the use is pretty hairy!
However, the following is a fairly basic problem, and if it cannot be
overcome, one would question the validity of having HANDLER at all. (read
that with a smile please).
My problem, I believe, is to do with table flushing. Any suggestions on how
to overcome this gratefully received.
(For the purposes of brevity in these tests, I do a TRUNCATE TABLE mytable
before all tests)
If I do an insert to a table from within my application, and then, from
another mysql session, do
HANDLER mytable OPEN;
HANDLER mytable READ FIRST;
then I get,
ERROR 1030: Got error 1 from table handler
However, if I do a
select * from mytable;
then I (as one would hope!) see my new data.
Further: If I try this on a table with just one column, then it works (i.e,
HANDLER can read it seemingly immediately). But if the table has a number of
columns (as below) then I see the above problem.
mysql> describe mytable; (output modified for
brevity)
id int(11)
status char(2) binary
lang_number int(11)
source_file char(20) binary
text_type char(10) binary
system char(4) binary
maximum_length smallint(6)
text char(132) binary
key_characters char(15) binary
first_revision int(11)
security_lock smallint(6)
default_option smallint(6)
+----------------+------------------+------+-----+---------+----------------
+
12 rows in set (0.00 sec)
As mentioned above, this feels like a flushing problem. So - how come select
can see the data? If HANDLER not reading the cache? Is this fixable?
I look forward to a response,
Many regards,
Ian Collins.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
