in
fields_changed columns of changedescs_changedescription but the text
is incomplete. Is there a way to disable the delta tracking for
Testing Done and Description fields or is there a way to inform
the user that his/her input is too long.
Thanks,
Ronak
--
Want to help the Review Board project? Donate
found out that if a user puts in a
long very long description in the Testing Done field and again goes
and changes that field the old and new comments are stored in
fields_changed columns of changedescs_changedescription but the text
is incomplete. Is there a way to disable
Christian Hammond wrote:
I don't know off-hand what we're going to set it to. We're thinking
about it, and suggestions are welcome. Here's where it gets tricky...
We're running up to maximum field lengths for the change info, and
that's a combination of multiple fields, including
We've done a little bit of testing with the server at VMware. There seems to
be a mix. We've had people try to dump ~1MB log files in for Description and
for Testing Done. Our Review Board admins there are beating people over the
head now to stop doing that, but given that we're seeing even that
there is always gzip ;-)
Which objects are we talking about here? Is it the table
changedescs_changedescription with column fields_changed? This could
be mapped to a CLOB so we are talking a total of 2Gb bytes for most
storage engines, there shouldn't be a noticeable limit for most back
ends
: fields_changed in changedescs_changedescription
Christian Hammond wrote:
We've done a little bit of testing with the server at VMware. There
seems to be a mix. We've had people try to dump ~1MB log files in for
Description and for Testing Done. Our Review Board admins there are
beating people over
