From 0ae9e6e8dd56af68a49329ad7ac4df5c978b7103 Mon Sep 17 00:00:00 2001 From: unknown <heikki@hundin.mysql.fi> Date: Fri, 17 Jan 2003 00:50:27 +0200 Subject: [PATCH] ha_innodb.cc: Had forgotten to change ha_innodb.cc to reflect that InnoDB now supports HA_READ_PREFIX_LAST sql/ha_innodb.cc: Had forgotten to change ha_innodb.cc to reflect that InnoDB now supports HA_READ_PREFIX_LAST --- sql/ha_innodb.cc | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/sql/ha_innodb.cc b/sql/ha_innodb.cc index f832106468..b4fe6130e9 100644 --- a/sql/ha_innodb.cc +++ b/sql/ha_innodb.cc @@ -2249,19 +2249,7 @@ convert_search_mode_to_innobase( case HA_READ_AFTER_KEY: return(PAGE_CUR_G); case HA_READ_BEFORE_KEY: return(PAGE_CUR_L); case HA_READ_PREFIX: return(PAGE_CUR_GE); - case HA_READ_PREFIX_LAST: - /* ut_print_timestamp(stderr); - fprintf(stderr, - " InnoDB: Warning: Using HA_READ_PREFIX_LAST\n"); */ - return(PAGE_CUR_LE); - - /* InnoDB does not yet support ..PREFIX_LAST! - We have to add a new search flag - PAGE_CUR_LE_OR_PREFIX to InnoDB. */ - - /* the above PREFIX flags mean that the last - field in the key value may just be a prefix - of the complete fixed length field */ + case HA_READ_PREFIX_LAST: return(PAGE_CUR_LE_OR_EXTENDS); default: assert(0); } -- 2.30.9