Re: [Sqlalchemy-tickets] [sqlalchemy] #1631: pg8000 not working with enums.

[sqlalchemy <mi...@zz...>]

#1631: pg8000 not working with enums.
-----------------------------------+------------------------------------
      Reporter:  guest             |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  medium            |  Milestone:  0.6.xx
     Component:  postgres          |   Severity:  no triage selected yet
    Resolution:  worksforme        |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+------------------------------------

Comment (by zzzeek):

 great.  not sure if you're aware, I created a fork of pg8000 that made
 extensive changes to the internals in the efforts of lots more speed and
 also extension capability.  It was specific to a database I was contracted
 to work with called Akiban, but the thrust of the internal changes was to
 do away with most of the internal object creation pg8000 uses in order to
 represent postgres structures.    I had emailed Mathieu about it but he
 did not respond.   the fork is at https://github.com/zzzeek/pg8000/ ,
 examples of major reductions in object creation can be seen at
 https://github.com/zzzeek/pg8000/commit/fffc22a5b92d849a23df8f46d1c54d3e98e9fba4,
 https://github.com/zzzeek/pg8000/commit/bc9127429b1a9df192d782198aee16488da0962f
 and
 https://github.com/zzzeek/pg8000/commit/b59841124f474fe14c69f7ff671e98f814447717
 where I tackle that huge parameter formatting function, it looks like you
 might have addressed this as well.   I have it supporting just the two
 formats that psycopg2 does instead of all of them.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1631#comment:8>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python