Development Discussion Board

I support having this permission in phpBB core as there very likely are cases where limiting access to IP addresses is (legally) beneficial; "principle of data economy" and "need to know" and all that.

Danielx64 wrote:Would this igo into 3.0 or 3.1?

Considering that it has been like that since forever, I would say that 3.1 is fine.

To me this just sounds like a bug that should be fixed. Feel free to have a look at the other tables as well.

Updated to 8ae315a796cc81b6ca4f423eb9bae20925f51fdb (phpBB 3.1.0-a2).

naderman wrote:There is no installation at all. After you upload files you can enable and disable the extension. We will not introduce the concept of an installation process simply because some people are used to it from Windows applications.

I completely agree.

I agree with the previous poster. This should not be part of phpBB core.

For future reference: An INDEX on an utf8 varchar(255) column has size 3*255 = 765 bytes. An INDEX on an utf8mb4 varchar(255) column will likely have size 4*255 = 1020 bytes. The maximum key size for a column is 767 bytes by default. As a result, varchar(255) columns may have to be reduced to varcha...

MySQL 5.0 is no longer maintained and MySQL 5.1 will probably be no longer maintained when phpBB 3.2 gets released, so this should be fine to do for phpBB 3.2 or 3.3.

I think this RFC can be rejected. At least for now, because there is nothing to do.

Background MySQL's "default" UTF8 character set only supports 3 byte characters which prevents the use of some characters such as http://en.wikipedia.org/wiki/Emoji. A 4 byte utf8 character set utf8mb4 has been introduced with MySQL 5.5. Proposal I propose upgrading all utf8 column charac...