Re: Engines, Fulltext Indexes, Transactions?
Posted by: Rick James
Date: November 18, 2009 07:05PM

I'll challenge "it is of absolute importance that all queries execute or none at all".

Suppose you do this:
INSERT INTO table_with_fulltext ...;
... rest of "transaction" -- INSERT into other tables...

Now let's say something fails. What will you have? You will have the text indexed, but not the rest of the stuff. And what happens when you go to look for it?

FROM table_with_fulltext
JOIN other_table ON ...

Well, the SELECT may waste some time looking that dead record, but it will still return the "right" answer, that is, no rows (because the JOIN will fail).

That is an example of how the SELECT side can cover for a "half written transaction". There are also examples of how INSERTing can leave the database OK, if not 'perfect'.

Options: ReplyQuote

Written By
Re: Engines, Fulltext Indexes, Transactions?
November 18, 2009 07:05PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.