List:Internals« Previous MessageNext Message »
From:Paul DuBois Date:October 7 2002 2:11pm
Subject:Re: bk commit into 4.1 tree [AUTO_INCREMENT for HEAP]
View as plain text  
At 17:49 +0500 10/7/02, ramil@stripped wrote:
>Below is the list of changes that have just been committed into a local
>4.1 repository of ram. When ram does a push these changes will
>be propagated to the main repository and, within 24 hours after the
>push, to the public repository.
>For information on how to access the public repository
>   1.1340 02/10/07 17:49:03 ram@stripped +12 -0
>   auto_increment for heap tables
>   test case


What are the specific behaviors of AUTO_INCREMENT for HEAP?

- Are values that are deleted from the top of the sequence reused
   (like ISAM and BDB) or not (like MyISAM and InnoDB)?
- Can you specify the initial AUTO_INCREMENT value with CREATE TABLE
   or change it with ALTER TABLE (like MyISAM)?
- Can you use AUTO_INCREMENT with a composite key to generate multiple
   sequences within a single table (like MyISAM and BDB)
- Does DELETE FROM tbl_name (no WHERE clause) reset the sequence counter
   to 1?
bk commit into 4.1 treeramil7 Oct
  • Re: bk commit into 4.1 tree [AUTO_INCREMENT for HEAP]Paul DuBois7 Oct