Jump to content

Topic on User talk:Brooke Vibber/Compacting the revision table round 2

user_entry and IPs and hex

4
Legoktm (talkcontribs)

In phab:T156318#3037271 there is a proposal to create a table that mostly adds a hex version of the IP addresses for easy searching of contributions in an IP range (what CheckUser already does). Is this something that should be considered in this revision schema re-do as it's basically an aggregate of the revision table?

CC @MusikAnimal

MusikAnimal (talkcontribs)

Yes, glad you brought this up :) With the revision re-do it would be wonderful if we could include a IP hex column or whatever you feel is best, such that we could easily query for IP ranges. That way when the time comes, we can adapt the Special:RangeContributions code to work off of it. In the interim we are hoping to move forward with our new table as planned, under the assumption the revision schema re-do is not going to happen anytime soon.

Legoktm (talkcontribs)

Oh yes, very much agreed on not waiting for this to implement the table for RangeContributions.

Brooke Vibber (talkcontribs)

If you need the index tied in with revision/timestamp order, then I think it'll work best as a separate table. That keeps the specialized indexes isolated, so they don't bloat the main revision table.

Reply to "user_entry and IPs and hex"