summaryrefslogtreecommitdiff
path: root/storage/example/ha_example.cc
diff options
context:
space:
mode:
Diffstat (limited to 'storage/example/ha_example.cc')
-rw-r--r--storage/example/ha_example.cc23
1 files changed, 0 insertions, 23 deletions
diff --git a/storage/example/ha_example.cc b/storage/example/ha_example.cc
index eeb9b12007b..3701957ec4f 100644
--- a/storage/example/ha_example.cc
+++ b/storage/example/ha_example.cc
@@ -822,29 +822,6 @@ int ha_example::delete_all_rows()
/**
@brief
- Used for handler specific truncate table. The table is locked in
- exclusive mode and handler is responsible for reseting the auto-
- increment counter.
-
- @details
- Called from Truncate_statement::handler_truncate.
- Not used if the handlerton supports HTON_CAN_RECREATE, unless this
- engine can be used as a partition. In this case, it is invoked when
- a particular partition is to be truncated.
-
- @see
- Truncate_statement in sql_truncate.cc
- Remarks in handler::truncate.
-*/
-int ha_example::truncate()
-{
- DBUG_ENTER("ha_example::truncate");
- DBUG_RETURN(HA_ERR_WRONG_COMMAND);
-}
-
-
-/**
- @brief
This create a lock on the table. If you are implementing a storage engine
that can handle transacations look at ha_berkely.cc to see how you will
want to go about doing this. Otherwise you should consider calling flock()