Jump to content

Problem to using innoDB to allow foreign keys?


cooldude832

Recommended Posts

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

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

 

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.