Last modified: 2014-06-05 10:22:52 UTC
Or, at least, more than a 15-character varbinary. At the moment, there is a hard 15-character limit on the contents of the rc_ip field in the recentchanges table. This was fine when we were on IPv4, but IPv6 has a maximum length of 39 characters. The result is IPv6 entries in the rc_ip field is currently being truncated, making them of little use to anyone. While the field isn't used for anything on production, it's a pretty common researcher/analyst resource. Thankfully cu_changes.cuc_ip is a 255-char varbinary, and so the same problem is not present there.
Autoblocks should also be checked, see Block::defaultRetroactiveAutoblock
For mysql the field is varbinary 40, so it is okay. Only for Oracle the field is still varchar2(15), which seems a problem. If you are looking at wmf tables than you should fill a site request to let a database admin alter all the wikis (Check one of the newer wikis first - all after r23239, if it okay there).
Raising priority. Data is being truncated.