List:Internals« Previous MessageNext Message »
From:Vyacheslav Akhmechet Date:May 14 2009 3:58am
View as plain text  

In my storage engine, when the server calls write_row, I read the
first field of the row in order to index on this field. I do it in the
following way:

    Field **field = table->field;
    long index = (*field)->val_int();

It works perfectly in release mode, but in debug mode val_int
generates ASSERT_COLUMN_MARKED_FOR_READ assertion (which is: "(!table
|| (!table->read_set || bitmap_is_set(table->read_set, field_index))),
function val_int, file, line 3682.")

What am I doing wrong? Do I need to mark the column for reading first?
Why? How does this affect the behavior of the server?

- Slava
ASSERT_COLUMN_MARKED_FOR_READ questionVyacheslav Akhmechet14 May
  • Re: ASSERT_COLUMN_MARKED_FOR_READ questionKristian Nielsen14 May
  • Re: ASSERT_COLUMN_MARKED_FOR_READ questionSergei Golubchik14 May
    • Re: ASSERT_COLUMN_MARKED_FOR_READ questionVyacheslav Akhmechet15 May