[Building Sakai] InnoDB Question

[Bryan Bakotich]

Sam,

Thanks for the info, I will give that a shot on our dev server.

If all tables should be InnoDB I think we should modify the documentation to
explicitly say that. It seems a little ambiguous how it's worded now
especially since a good portion of the tables are created as InnoDB even if
it isn't the default storage engine.

Maybe we could add something like this (which is a little info note in
atlassian's confluence setup guide):
*It is* *highly recommended* *that you only use the InnoDB storage engine
with Confluence. Avoid using the MyISAM storage engine as this can lead to
data corruption.*

Or we could append something like &sessionVariables=storage_engine=InnoDB to
the jdbc url in the default sakai.properties file so that people don't have
to modify the default storage engine.

Any thoughts?

-Bryan

On Wed, Oct 20, 2010 at 5:48 PM, Sam Ottenhoff <ottenhoff at longsight.com>wrote:

>  I strongly recommend using only InnoDB.  All tables should be InnoDB.
> Using only InnoDB will provide transaction support, foreign key support, and
> will make sure you are running on the same database engine as other Sakai
> MySQL users.
>
> I recommend stopping Sakai, doing a MySQL database dump, changing all table
> creation stanzas to use InnoDB, and re-importing the database.  Finally, I
> recommend starting a clean instance of Sakai 2.7 to compare it your
> newly-converted InnoDB database.  If you have any missing foreign keys in
> your converted database, you will have to resolve duplicate data manually
> and apply the foreign-key constraints manually.
>
> --Sam
>
>
> On 10/20/2010 8:31 PM, Bryan Bakotich wrote:
>
> Hi,
>
> On the Sakai 2.7 install guide it says this about MySQL and InnoDB: Sakai
> requires transaction support. In the case of MySQL you must implement the
> InnoDB storage engine to ensure proper transaction handling.
>
> Does this mean that InnoDB just needs to be an available storage engine or
> should this be the default storage engine so that all tables are InnoDB? I
> am asking this because our current 2.6.x database is a mix of MyISAM and
> InnoDB and I just ran into an error while running the
> sakai_2_7_0_mysql_conversion.sql script because one of our existing tables
> was MyISAM and it needed to be InnoDB.
> I also recently did a fresh 2.7 install for a non-profit and their database
> has a lot more InnoDB tables than ours (Our current installation has 118,
> fresh install has 199).
>
> So should all tables be InnoDB or just a few? Is it documented anywhere
> what tables should be what storage engine so I can make sure our database is
> correct? Thanks for the help!
>
> -Bryan
>
> --
> Bryan Bakotich
> Open Source Implementation Specialist
> Digital Media Center, Information & Technology Services
> Pacific Lutheran University
> Tacoma, WA 98447-0013
> Phone: 253-536-5021
>
>
> _______________________________________________
> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>



-- 
Bryan Bakotich
Open Source Implementation Specialist
Digital Media Center, Information & Technology Services
Pacific Lutheran University
Tacoma, WA 98447-0013
Phone: 253-536-5021
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/68abdd77/attachment.html