--
Mike Orr <slugg...@gmail.com>
Sounds good to me... let's do it via IRC.
- C
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "pylons-discuss" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/pylons-discuss/-/slLygKle4q8J.
> To post to this group, send email to pylons-...@googlegroups.com.
> To unsubscribe from this group, send email to pylons-discuss
> +unsub...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-discuss?hl=en.
That looks fine.
The second half of that article I'm not so hot about, a configuration
that depends on config.scan(). Akhet has avoided that so far.
So would you use SQLAHelper at all then? It basically acts as a shared
container for the dbsession, engines, and declarative base. Perhaps
for simplicity you could drop it for the default configuration, and
just mention in the documentation or comments that it's useful for
multi-db or multi-module models.
--
Mike Orr <slugg...@gmail.com>
I wrote a package basically for managing SQLALchemy sessions in Pyramid
applications:
http://packages.python.org/mortar_rdb/use.html
Ignore the schema versioning stuff if you want, it's not a necessary
part of the equation...
any problems, shout my way...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk