Database table names MUST have a prefix.

[martti]

This is a bit retarded, isn't it?

[DavidIQ]

Why?

[martti]

That database table names MUST have a prefix.

[david63]

But if, as some do, have multiple phpBB installs in the same database then you need the prefix to distinguish them.

It is probably a carry over from the days when many hosts only allowed one database in an account, unlike today where usually you can have several - if not unlimited.

The problem if the prefix was removed would be where you have the inexperienced user who creates multiple instances of phpBB in the same database - and there are still many of those around if you follow the support topics.

[DavidIQ]

Besides what David said there is the problem of other systems living in the same database, like WordPress and Drupal. If there were no table prefixes then you'd have a big problem. Think of the users and posts table for instance which can be in WP as well.

[martti]

The problem is that phpBB is telling inexperienced people that throwing everything together in one database is the standard way to organise things. Better not feed ignorance.

Too much is carried over from the old days! When it's dustbin day, you'll need to put the dustbin out, otherwise the garbage piles up in the house.

The inexperienced user I would guide carefully in the direction of SQLite3. Super easy (hence the name "lite") and you can have as many as you like. There is also a nice program to manage it online, phpLiteAdmin.

[DavidIQ]

Having separate databases for everything is not always possible so making assumptions about what a user can and cannot do with the plan they've purchased for their site, especially in the case of shared hosting, is not something we should do. There are other reasons too. What if I wanted to create a table or two for something else? With your logic I should be creating an entire database just for that. So no it's not a superfluous thing to ask for a table prefix during setup.