Yes, a certain level of frustration is bound to occur after you have
spent an hour reading about the project, downloading the code and
setting up an example - only to find a show stopping bug, report it
some time later after finding the right bug tracker... to then notice
that there hasn't
I'm still around; unforunately, I'm afraid I lack the time/motivation
to put much more into migrate. I've no objections to someone else
taking over the project, if anyone's interested.
For what it's worth, there's a mostly-finished svn branch that removes
monkeypatching, no changes to SA
I was considering the use of migrate (http://erosson.com/migrate/) for
a new project using SA and I just wondered if anyone else is using
it?
I'm using it, but then, I wrote it. It's worked well for me, though
I'm not sure how widely used it is... the mailing list is pretty
quiet.
Are there
Migrate? I'm afraid not. It only uses a version number on the database
to keep things synced, and expects that this version number is
incremented every time the schema is changed. (Migrate manages the
version number.) There's no comparison of tables/triggers/functions to
ensure that's correct.
Excellent, thanks. Wasn't sure whether you were still hanging around
on the SQLAlchemy list or not, which is why I said Anyone want to
tackle this?.
Yup, I'm still around, though the times at which I read the list can
be a little erratic.
Posted migrate 0.2.1 earlier today; it should work
