cooldude832 Posted August 11, 2008 Share Posted August 11, 2008 I've got a lot of tables that could be manged a lot easier using foreign keys but I'm wondering if using innoDB engine or MyISAM is going to be an issue. Specific tables are: Users User_Functions Uses_Grant_Functions (links users and functions up) Quote Link to comment Share on other sites More sharing options...
elflacodepr Posted August 11, 2008 Share Posted August 11, 2008 innoDB support foreign keys Quote Link to comment Share on other sites More sharing options...
cooldude832 Posted August 12, 2008 Author Share Posted August 12, 2008 I meant to saying is using innoDB over MySQL gonna cause a problem. Quote Link to comment Share on other sites More sharing options...
fenway Posted August 12, 2008 Share Posted August 12, 2008 I meant to saying is using innoDB over MySQL gonna cause a problem. It's most definitely slower. Quote Link to comment Share on other sites More sharing options...
cooldude832 Posted August 12, 2008 Author Share Posted August 12, 2008 Is it so much slower that its a problem you think? Quote Link to comment Share on other sites More sharing options...
Barand Posted August 12, 2008 Share Posted August 12, 2008 If you need automatic enforcement of referential integrity and cascading deletes/updates then it's INNOdb. If they are not essential, it's MyISAM Quote Link to comment Share on other sites More sharing options...
cooldude832 Posted August 13, 2008 Author Share Posted August 13, 2008 Well i'm writing functionality where people could get into the backend and mess with stuff so the syncing could be issues so Quote Link to comment Share on other sites More sharing options...
Barand Posted August 13, 2008 Share Posted August 13, 2008 Then in that case the alternative to automatiic integrity is enforcing your own. INNO may be slower (than MyIsam) but probably far more efficient than the DIY approach. So if you don't need fulltext I'd use INNO Quote Link to comment Share on other sites More sharing options...
cooldude832 Posted August 13, 2008 Author Share Posted August 13, 2008 Well I have already determined that innoDB is fine because the only sections that need fulltext will be in a separate table isolated from innoDB. If a user changes an ID linking to this fulltext table then the search function can't find that page. Oh well no big deal. If you wondering what I'm doing I'm finalizing my CMS system and basically I am syncing all the backend functions up but IDs might be changed so I wanted to keep it safe. The fulltext area is the content area of pages, but what I am doing is storing it twice in 1 table its innoDB to the users table so I can keep track of who altered content area last etc. The second table will be MyISAM and store the data in a methodical method by pulling h1,h2,h3,h4,h5 tags and page title keywords etc. It will also store the content area with stripped tags for the full text affect and then sort results based on matches in page title then matches in H1-H5 then by num of matches in content block Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.