Important: Tags unusable in 4.1 for the next few days/weeks + possible dataloss

Frédéric Buclin lpsolit at
Sun Jan 30 13:56:37 UTC 2011

Hi all,

Two important news you should know about:

I committed bug 616185 less than two hours ago which moves tags into
their own DB tables. Till is fixed to go look at these new
tables to retrieve them, tags will be unusable in queries for the next
few days/weeks (this is intentional!). You can track progress in bug
616341. To be clear: this means that you can still add and remove tags
from the footer of the page (for those who have enabled this feature),
but you will not be able to run queries based on tags till bug 616341 is
fixed. The data is there, but you cannot access it yet.

Less pleasant: When I committed bug 616185, I incorrectly parsed queries
to extract bug IDs, because 1,2,3 was stored as 1%2C2%2C3 in the DB,
i.e. commas where encoded as %2C (in Bugzilla 3.x and 4.0, but not in
2.22), but my regular expression used [\s,]+ directly, unencoded. On
PostgreSQL, this means that would fail, complaining that
you tried to insert a string into an integer field. On MySQL, it would
silently discard everything after the first bug ID, resulting in
dataloss. So if you upgraded your 4.1 installation between 4:07am and
4:56am PST (12:07 and 12:56 GMT) today, then you may have to use your
backup to restore the DB. If your installation doesn't use bug tags,
then you are not affected. If you use PostgreSQL and
didn't complain, then you are not affected. Also, Bugzilla 4.0rc2 and
older are not affected by this checkin as I didn't commit my patch on
these branches.

Sorry for the inconvenience,


More information about the developers mailing list