[sqlalchemy] Re: Future of migrate project
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 been a check-in for some months and to then have to spend a further 15 minutes checking various places to try and find it's status. Sorry about that. There's a warning on migrate's front page now. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
[sqlalchemy] Re: Future of migrate project
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 required: http://erosson.com/migrate/trac/browser/migrate/branches/monkeypatch_removal Haven't moved it to trunk/released it because I never got around to fixing constraints. Looks like it may be out of date once again too; but if anyone's up for taking over migrate, it's a better place to start than trunk. On 6/27/07, Michael Bayer [EMAIL PROTECTED] wrote: Based on the non-responsiveness on the migrate ML, I think migrate needs someone to take it over at this point. I would favor a rewrite that doesn't rely upon any monkeypatching within SA (which would have prevented the breakage upon version change), and I also had agreed earlier to allow ALTER TABLE hooks into SA's dialect to smooth over those particular operations which currently are bolted on by migrate's current approach. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
[sqlalchemy] Re: Anyone using migrate?
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 any plans to integrate this support into a future version of SA? Nope. Discussed this a while back, and the decision was to keep things separate; the SA core has plenty to do already. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
[sqlalchemy] Re: Migrations
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. On 10/27/06, Jonathan Ellis [EMAIL PROTECTED] wrote: I have two databases that are supposed to be kept in sync. I suspect that because of human error they might not be. Can Migrations help compare tables, triggers, functions and tell me what doesn't match? -- Jonathan Ellis http://spyced.blogspot.com -- - Evan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: Changes in SA 0.3 cause migrate 0.2 to fail
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 with SA 0.3. -- - Evan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
