P
P
pyatin2011-06-20 02:12:01
MySQL
pyatin, 2011-06-20 02:12:01

MySQL InnoDB + MyISAM

Good day.

Actually a question whether it is normal to use various types of tables in one database?
What is the risk?

The need to use innoDB + MyISAM in one of the projects is that - you need full-text search + transactions and integrity constraints.

Perhaps there are more suitable subds for such a task, but one of the requirements is the use
of mySQL in the project.

Answer the question

In order to leave comments, you need to log in

5 answer(s)
S
sl_bug, 2011-06-20
@sl_bug

And it is impossible to hang up full-text search on sphinx for example? And then all tables in innoDB.

V
Vitaly Zheltyakov, 2011-06-20
@VitaZheltyakov

Yes, you can safely use it without any problems.
A couple of rules for such systems (from personal experience):
- Do not make joint change requests. It is better to query each type of table separately.
- Linked field types must be exactly the same.
- For backup use save to dump. No copying of files is fraught with data corruption.

M
Mark, 2011-06-20
@printf

The search for truth is better to take out. In general, they can be used together, sometimes they do. Transactionality and foreign key checks will not spread to MyISAM, the rest will work.

@
@resurection, 2011-06-20
_

There will be problems with transactions. rallback will work strangely: it will roll back only part of the changes - the part that was made in InnoDB. And that which in MyISAM will leave. Naturally, this will manifest itself not only on rallback, but it may manifest itself, for example, when the server crashes, when foreign keys do not have time to work, the transaction will be partially rolled back.

K
Konstantin, 2011-06-20
@Norraxx

PostgreSQL + tsvector

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question