On Tue, Dec 27, 2011 at 1:54 AM, Chris Withers <[email protected]> wrote:

> Yeah, I kinda feel the same way, and I guess I'm a bit bummed that my
> perception is that people have consistently ignored mortar_rdb, which covers
> exactly the same territory. More galling for me is that it's existed since
> early 2010, but I wasn't allowed to open source it until early 2011.

> Still, I'd like to know what I did wrong that meant people just ignored it.
> My only guess here is that mortar_rdb felt "too heavyweight", given the
> (optional) mention of sqlalchemy-migrate in the usage docs? Or maybe I
> didn't publicise it enough? Seriously, I'd like to know, since I feel the
> same about testfixtures and mailinglogger...

I didn't know it existed. I don't go looking on PyPI for things unless
I need something in particular. And this is the kind of thing you may
not know you need.

The migration part is fine for a utility, but it's too heavy-handed
for a dependency you want everybody to use. I for one am reluctant to
use any migration utility because it's one more thing to learn and a
potential point of failure. For small changes like adding a column or
changing its type, I just do it directly. For large changes I make a
bin script.

> Nonetheless, things SQLAHelper is missing from my perspective:
>
> - the ability to pass parameters to the declarative base
>  (see
> http://packages.python.org/mortar_rdb/api.html#mortar_rdb.declarative_base)

That's what ``set_base()`` is for.

> - control over the session that is stored. As I read it, you'd need to call
> Session.configure in every request.
>  (see
> http://packages.python.org/mortar_rdb/api.html#mortar_rdb.registerSession)

You only need to call it at the beginning of the application, once you
have your engine.

-- 
Mike Orr <[email protected]>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to