Preventing phantom reads with Read Commited isolation

[xxxx xxxxx]

Hello everyone.

When performing transactions i usually start the transaction with a read commited isolation , with an optimistic approach ,and than i can switch to pessimistic approach for certain database access parts of the transaction by specifying table hints to lock rows.

I learned that in innoDB we use SELECT....FOR UPDATE to prevent non repeatable read.

How about phantom rows,is there a hint to prevent insertion?