drizzled::ReadRecord::init_read_record_idx ignores startIndexScan result

Bug #697984 reported by Stewart Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Stewart Smith
7.0
Fix Released
Medium
Stewart Smith

Bug Description

drizzled/records.cc: In member function ‘void drizzled::ReadRecord::init_read_record_idx(drizzled::Session*, drizzled::Table*, bool, uint32_t)’:
drizzled/records.cc:64: error: ignoring return value of ‘int drizzled::Cursor::startIndexScan(uint32_t, bool)’, declared with attribute warn_unused_result [-Wunused-result]

Related branches

Revision history for this message
Stewart Smith (stewart) wrote :

this propagates up into sql_delete

cc1plus: warnings being treated as errors
drizzled/sql_delete.cc: In function ‘bool drizzled::delete_query(drizzled::Session*, drizzled::TableList*, drizzled::COND*, drizzled::SQL_LIST*, drizzled::ha_rows, uint64_t, bool)’:
drizzled/sql_delete.cc:254: error: ignoring return value of ‘int drizzled::ReadRecord::init_read_record_idx(drizzled::Session*, drizzled::Table*, bool, uint32_t)’, declared with attribute warn_unused_result [-Wunused-result]

Revision history for this message
Stewart Smith (stewart) wrote :

also into sql_update. i.e. there are a few places this could be a problem :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.