Aryeh Gregor <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |
            Summary|Change                      |Allow comments longer than
                   |rev_comment/log_comment     |255 bytes
                   |from TINYBLOB to BLOB       |

--- Comment #15 from Aryeh Gregor <> 2010-03-02 
18:58:18 UTC ---
How about this.  Add new rev_text and log_text as foreign keys to old_id.  If
the comment fits in rev_comment/log_comment, keep it there, and set
rev_text/log_text = 0.  Otherwise, keep a truncated version in
rev_comment/log_comment and use that for RC and watchlist, and set
rev_text/log_text and use that on history pages and other appropriate places. 
(We probably don't want super-long summaries on RC anyway, it would add

We'd likely have a limit of 1000 Unicode characters or less, though, so would
using the text table be overkill?  Would it make more sense to just have
rev_comment_long/log_comment_long or something?

Either way, this scheme wouldn't increase the database size noticeably for 95%+
of revisions, since most people aren't that verbose.  So that shouldn't be a
big problem, right?

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

Wikibugs-l mailing list

Reply via email to