The issue is that the system is planned with multi-domain support. There is an idea for each domain to create their own tables. Well, naturally, in order to remove the flow of queries to a single table. Because if it will be several sites, then different tables should, in theory, help to remove the brakes associated with the execution of UPDATE.

But, on the other hand, it is a bad form or something. Actually, what do you say?

Closed due to the fact that off-topic participants aleksandr barakin , ixSci , Vladyslav Matviienko , Nick Volynkin ♦ , Mirdin 21 Jul '15 at 8:20 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • " Questionnaires are forbidden on Stack Overflow in Russian . To get an answer, rephrase your question so that it can be given an unambiguously correct answer." - aleksandr barakin, ixSci, Vladyslav Matviienko, Nick Volynkin, Mirdin
If the question can be reformulated according to the rules set out in the certificate , edit it .

    1 answer 1

    Use different databases and mysqli ...
    IMHO ...

    • Well, in the old version, I still used mysqli, now I decided to switch to PDO. But I didn’t quite understand about single-time databases, do you offer to completely duplicate user settings and all that? But it will also create new problems, for example, general authorization will be more curly-headed. - Arni
    • I had to enter the content characteristic of a site to break into different databases, for general, you can create your own database such as General there, I do not know ... In any case, I would definitely do just that ... - Zowie