> > > On Wed, Nov 11, 2009 at 11:40 AM, Nigel Kukard <[email protected] > <mailto:[email protected]>> wrote: > >> On Wed, Nov 11, 2009 at 12:58 AM, Nigel Kukard <[email protected] >> <mailto:[email protected]>> wrote: >> >> > Hey, >> > >> > Is it possible to change the Storage engine of tables namely >> > "quotas_tracking" & "session_tracking" >> > & Would the change hamper the performance of Cluebringer ? >> I think it >> > would. >> > >> > Reason I'm asking is both tables are using FOREIGN KEYS >> which aren't >> > supported by MEMORY Engine in MySQL. >> > >> > Also is there any workaround ( apart from keeping the >> storage engine >> > to InnoDB ) ? >> >> Try removing the foreign keys from the schema and trying with >> the memory >> engine. >> >> >> Yes It worked, as I said converting it wasn't a problem, also >> noticed 1 more thing with "session_tracking" table which has a >> cloumn "RecipientData" which has data type "text" which isn't >> supported by MEMORY engine. >> >> I might as well use varchar similar to other columns. >> >> I would like to know will there be any performance issues with >> cluebringers because of missing FOREIGN KEY ? >> Please suggest. >> > > varchar should work just fine for the column type. > > Unfortunately I don't personally have any benchmarks comparing > MEMORY to INNODB. > > -N > > > What I mean to convey is by removing the foreign key, will cluebringer > be able to keep track of mail / message count against the policy ( > Quotas ) that I'd be creating, Will it still function ( reject / allow > sender ) the same way ? > > This is what I would like to know.
Yep, just index the columns used in the foreign key and it should be ok. :) ... it works with myisam which doesn't honor foreign keys (iirc). -N
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
