From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
---|---|
To: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
Cc: | psycopg(at)postgresql(dot)org |
Subject: | Re: little_pger.py (a thin layer a tad above SQL and psycopg2) |
Date: | 2012-12-19 17:12:16 |
Message-ID: | 20121219171215.GA15802@campbell-lange.net |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 19/12/12, A.M. (agentm(at)themactionfaction(dot)com) wrote:
>
> On Dec 19, 2012, at 11:53 AM, Rory Campbell-Lange wrote:
>
> > On 19/12/12, A.M. (agentm(at)themactionfaction(dot)com) wrote:
> >> ...I, too, have been looking for something lightweight and quick which
> >> would allow nearly-automatic JSON generation from database rows. The
> >> trickier part is recursing a model attribute tree which always leads
> >> me back to SQLAlchemy.
> >
> > Since psycopg can return namedtuples and simplejson serialises
> > namedtuples, this should not be a difficult thing to do.
>
>
> That doesn't help when there are columns or subselects which need to
> become part of a one-to-many or many-to-many relationship represented
> as arrays attached to the main model in JSON. That is what I meant by
> "recursing the model attribute tree".
Ah -- we do that sort of thing in the database.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2012-12-31 20:20:04 | Repository |
Previous Message | A.M. | 2012-12-19 16:56:35 | Re: little_pger.py (a thin layer a tad above SQL and psycopg2) |