Roland Rosenfeld wrote: > On Tue, 18 Mar 2008, Cami Sardinha wrote: > >> Policyd was test/written for MySQL 4.x. This doesn't mean it >> shouldn't behave the same for v5. Unless i'm mistake (or things have >> changed between versions), using "DELETE QUICK" on an >> auto-incrementing row is where holes (/fragmentation) occurs. This >> was one of the reasons that Policyd has no auto-incrementing >> fields. Is this no longer the case with MySQL v5? > > As I understand this, the timestamp columns cause the same problem > that auto-increment columns imply
I've yet to find any documentation to state that the same occurs for standard INT(or TIMESTAMP) types. We are using INT's and from what i read in the MySQL documentation, there is no fragmentation caused by it. CREATE TABLE triplet ( _from char(60) NOT NULL default '', _rcpt char(60) NOT NULL default '', _host char(15) NOT NULL default '', _datenew int(10) unsigned NOT NULL default '0', _datelast int(10) unsigned NOT NULL default '0', _count smallint(5) unsigned NOT NULL default '0', UNIQUE KEY _host (_host,_from,_rcpt), KEY _datelast (_datelast), KEY _datenew (_datenew) ) TYPE=MyISAM; Cami ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
