I wish I was online over the holidays to take part in this discussion. Here's my .02ยข :
- I think SqlAlchemy is the best ORM out there, and it's honestly been the deciding factor for me going with Pylons and sticking with Pyramid. - I think Pyramid core really needs to have a concrete DB/ORM plugin functionality / method / api / style. Whether you use SqlAlchemy or ZopeDB or something else, I think Pyramid should have a standard / recommended and documented place + support for starting up the DB connectivity. This doesn't need to be lines of code , it could just be a very well documented coding style / paster template. - I think the SqlAlchemy support needs to handle one or more databases , and both declaritive and reflective styles ( is there a third kind )? Pyramid is simply too free / open ended right now in regards to database support. It has the most potential out of all the frameworks, but its just frustrating at times. I started with the stock sqlahelper, and have been hacking at my integration to get more core SqlAlchemy functionality that it no longer resembles anything in published docs... if i had to hand this project over to someone else, i'd be worried that its so custom. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
