Hello there,
I'm looking into the cheapest way of, in core, building collections into
each row on fairly large left and right tables (the collections themselves
are small though). By collection i mean the same thing as in sqlalchemy
orm: an outer left join, that to each row of the left table with
Nice! I did not associate the custom typing in the docs with this
functionality before. It would have saved me a lot of time!
Thank you very much again!
g.
On Tue, Oct 8, 2013 at 7:12 AM, Michael Bayer mike...@zzzcomputing.comwrote:
On Oct 7, 2013, at 10:26 PM, tiadobatima gbara...@gmail.com
Thanks Askel... You still made me think about doing the reflection of all
tables upfront when the app starts... When there are too many tables, this
can add up to startup time.
It would be great if we could easily subclass Table though :)
Cheers,
g.
On Thu, Aug 8, 2013 at 4:50 PM, askel
a subclass of Table with your extra methods,
then iterate over each table in the metadata, setting the __class__
attribute to your subclass.
Hope that helps,
Simon
On Thu, Aug 1, 2013 at 12:17 AM, Gustavo Baratto gbara...@gmail.com
wrote:
Thanks for the reply Michael... I had a hunch
Hi Askel...
What I'd like to accomplish is to add few more attributes and methods to
Table (or maybe override insert/update/delete/select) to do post
processing of the Result/Row proxies and return them in different formats
such as json, yaml, xml, etc... so, while you suggestion is really neat,
Thanks for the reply Michael... I had a hunch this wouldn't be easy to
tackle, but this is more than I can chew at the moment: )
For now, I'll just keeping doing what I'm already doing which is to
instantiate a new class taking the table as an argument, and then within my
class reference the
