Am 2014-11-14 um 18:05 schrieb kcrisman: > > Per the recent discussion I will not batch modify the milestone on the > currently-open tickets. > > > Thank you. > > Did we end up discovering what the secret sauce was for doing it on the > database > directly?
If the database schema at http://trac.sagemath.org/wiki/DBSchema is accurate, update ticket set milestone='sage-6.5' where milestone='sage-6.4' and status != 'closed'; could be the trick. Before trying that, I'd like to see what select id, summary, milestone, status from ticket where milestone='sage-6.4' and status != 'closed' actually gives. However, the above lines are hardly secret sauce ... Regards, CH -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
