[Twisted-Python] Twisted and Postgresql

[Edmund Dengler]

I tried doing it as one of my steps (which is how I ran into the PgInt2
issue when I just did the top level). This is probably easier than
jelly-ing everything, and probably not all that much work (a couple of
hours?), just hoping that there was an already done solution.

Regards!
Ed

On Sun, 10 Aug 2003, Itamar Shtull-Trauring wrote:

> On Sat, 9 Aug 2003 18:19:25 -0400 (EDT)
> Edmund Dengler <edmundd at eSentire.com> wrote:
>
> > When trying to transfer a row set, which was obtained using the
> > pyPgSQL module, I am having problems with specific types not being
> > jelly-able. In particular, the row itself
> > PgResultSetConcreteRow(?)(this is from memory) and PgInt2 (which I
> > found out by trying to send individual elements of the row set over).
> > Has anybody else encountered these, and is there a solution other than
> > defining my own set of jelly-able components (for example, is there a
> > stock jelly library someplace)?
>
> Just convert them into lists and ints or dicts, the applicable python
> object that the pypgsql type emulates. SO, write a function that
> recurses a postgresql result and cleans it up, and then addCallback it
> to the Deferred of the database query result.
>
> --
> Itamar Shtull-Trauring    http://itamarst.org/
> Available for Python & Twisted consulting
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>