Test before comitting to production. I have done the same gradual
updates in essence, and I haven't found issues so far. But better safe
than sorry; copy your production database, and test the trunk version
against that. I'm using postgresql, and there's a bit of straight SQL
in the code that wasn't there in r10; it is simple enough SQL, but not
tested against mysql. The query in question is:
update agilito_userstory set rank = rank - 1 where project_id=%s
and rank > %s
which looks to be non-db specific to me. The other bit is:
select distinct
p.id,
p.name
from agilito_project p
join agilito_project_project_members pm on pm.project_id =
p.id and pm.user_id = %(me)d
join agilito_iteration i on i.project_id =
p.id
where i.start_date <= '%(today)s' and i.end_date >= '%
(last_end)s'
order by
p.id
where the dates are in '%Y-%m-%d' format. I think pretty much any
database supports this date format.
Let me know how it goes.
Emile