Re: [Fwd: Re: [sqlalchemy] Book]
On Sat, Jan 16, 2010 at 11:29 AM, werner wbru...@free.fr wrote: Seeing that Mark Ramm is co-author of this book, will it cover TurboGears in any why when it comes out? It has been massively postponed, but it's not altogether stopped. I've been working some the last two weeks to try to get it unjammed and going again. Chances are that it will not partiularly cover TurboGears, but that it might use TG or Pylons in some examples, along with Django and some desktop GUI toolkit or other. --Mark Ramm -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
[sqlalchemy] SQLAlchemy schema migrations: Oracle tester needed
Migrate, the SQLALchemy migration tool has a new home and a new name. You can find the new improved sqlalchemy-migrate at: http://code.google.com/p/sqlalchemy-migrate/ Jan Dittberner and dykang have done the nessisary work to get migrate back into a functional state for SQLAlchemy 0.3.10, and that work was merged into trunk today. There are plans to do the SQLAlchemy 0.4 migration as soon as possible and release a sqlalchemy-migrate packate that is 0.4 compatable. But right now we need people who are willing to test migrate on 0.3 and let us know if everything works -- in particular we need someone who has a full oracle licence to test and see if migrate works there (we have failing oracle test, but we're not sure if it's the result of 10g XE limitations, or if the oracle support is actually broken). There's a to-do list on the wiki at: http://code.google.com/p/sqlalchemy-migrate/wiki/Todo Any input/help/advice/critique from the community is welcome. When I talked about SQLAlchemy at PyCon the issue of Migrations was one of the most discussed features, and I would really like to see world class migration support in SQLAlchemy to go along with all of it's other world class features ;) -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~-~--~~~---~--~~ 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] Fwd: Migrate: svndump loaded into google code project
I thought this might be of interest to many of you. We've been trying to gather up a few people to and revive the floundering SQLAlchemy migrations project. There's actually some pretty good code there already, it just needs a bit of love and tenderness to get it up to date wth SQLALchemy 0.4. It would be a huge benefit to have a clear story to tell in the python world about how to do agile database development, or just how to manage database upgrades as your application evolves. If you feel up to it, join the mailing list, ([EMAIL PROTECTED]) look over the code, ask some questions, and get involved. --Mark -- Forwarded message -- From: Mark Ramm [EMAIL PROTECTED] Date: Oct 2, 2007 11:39 AM Subject: Re: Migrate: svndump loaded into google code project? To: [EMAIL PROTECTED] I just loaded Evan's svndump into the shiny new google code repository at: http://sqlalchemy-migrate.googlecode.com/svn/ Now everything is ready to start the work on reviving migrate. Thanks Jan! Just a reminder, I think we should work on getting the monkey patch removal branch working with 0.3.10 first. I think someone may have even completed this work, if so now would be a great time to check that in. ;) Once that's done I would propose moving that branch to trunk and working on making it 0.4 ready. --Mark -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~-~--~~~---~--~~ 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: major help required with SQLAlchemy and Turbogears.
Great. This gives us a very good reason to shift everything we have to Pylons. I like the fact that Pylons gives us that controller as I think that control is very important in developing a robust application. I want to know what goes one versus having the framework do everything for me. Moving to pylons now. You can also turn off automatic transaction handling in TurboGears. It's a one line config change, and then you are back in controll of your transactions. But the on/off switch is a bit too course grained for what we ultimately want, so TG 2 will have a much more configurable transaction system. --Mark --~--~-~--~~~---~--~~ 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: major help required with SQLAlchemy and Turbogears.
it appears that they are binding their metadata to a connection completely distinct from the one they bind their SessionTransaction to, is generally disastrous for a straight SQL statement like table.update(). This is something we should fix in the 1.x line, and make sure we don't replicate in the 2.0 transaction managment middleware when that gets built. --~--~-~--~~~---~--~~ 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: TurboEntity announcement
I've seen some other TG-named stuff (Turbo(Mail|Setup)) that only looks to work with TG, so some people might assume that about your project as well (if they're lazy and don't read). I think the turbo prefix may not always mean that it's intended for use with TurboGears. Turbogears is spinning off some core parts (widgets in particular) into framework independent libraries. And those may also have the Turbo prefix. But really I don't think the lack of a naming convention will create too much trouble. It is worth a mention on the TurboEntity site though! --Mark Ramm www.compoundthinking.com/blog --~--~-~--~~~---~--~~ 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: TurboEntity announcement
Right, TGWidgets. I wasn't suggesting it would cause mass confusion or anything, just that since it's its own thing, being under the TG namespace makes it look related to TG as opposed to a something that works well with TG but just as well without. Yep. Makes sense. I just noticed that it's called TGWidgets because TurboWidgets is already taken, and it's NOT a TurboGears or even a Python related project. The namespace confusion is inescapable! -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
