[rt-users] Sessions Table is MyISAM - RT 3.8.4

[Jesse Vincent]

On Mon, Sep 21, 2009 at 07:15:09PM -0700, Behzad Mahini wrote:
> I have done a fresh installation of RT 3.8.4,  and have done no  
> modifications of any sort to the default installation.....and was  
> preparing to do my database backup (using mysqldump),and noticed the  
> only table that has a MyISAM engine is the 'Sessions' Table (the rest  
> are all InnoDB as expected).
> 
> My understanding is that all of these tables were to have been of the  
> InnoDB engine type (RT's transaction-based requirements/ 
> recommendations).
> 
> 1) Is this by design, or due to an unresolved bug?

Closer to the former than the latter. 

> 2) If this is due to a bug, what is the remedy?

You can use mysql's standard recipe for converting it to an innodb
table.

> 3) If this is by design, what steps need to be taken when it comes to  
> MySQL backup, as I will have a combination of InnoDB and MyISAM based  
> tables. Note: Per MySQL documentations, InnoDB tables need to be  
> backed up with '--single-transaction' flag of mysqldump, and MyISAM  
> tables need to be backed up with 'lock-tables'....and the two  
> mentioned flags are mutually exclusive 
> (http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html ).

Bascially, it's unimportant to back up the sessions table. It's just
user sessions.  The worst case scenario is that your users will need to
log in again after restoring from backup.

> 
> My Environment:
> 
> RT 3.8.4
> Mac OS X 10.5.8
> MySQL 5.1.37
> Apache/2.2.13 (Unix) mod_perl/2.0.4 Perl/v5.8.8 configured
> 
> 
> Thanks,
> Behzad

> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com

--