it might be hitting?
On 7/8/14, 5:56 PM, Jason Newton wrote:
Any thoughts on why the unit testing is failing?
platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 --
/usr/bin/python
== 5776 passed,
688 skipped in 139.77
problematic.
issue appeared in 0.9.6, not 0.9.5 ?
On 7/9/14, 3:01 AM, Jason Newton wrote:
Yes, it seems to me like it gets to the end and then commits suicide just
before returning, but I wasn't able to make heads or tails.
Nothing fancy to running it - just unpack the pypi archive
Any thoughts on why the unit testing is failing?
platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 --
/usr/bin/python
== 5776 passed, 688
skipped in 139.77 seconds
===
Hi,
I'm wondering how I might get at postgresql's large object type (lob).
It's not to be confused with the TOASTED bytea, which are limited currently
to 1 GiB yet in practice is much lower (for me 400MiB) - it's a special
table + api designed to handle very large binary objects, like a few
Hi,
I've replied inline below.
On Wed, Jun 25, 2014 at 6:46 AM, Mike Bayer mike...@zzzcomputing.com
wrote:
well we just added the OID type in 0.9.5, so you at least have that.
I came across the entry on the issue tracker a little bit after
submitting. As usual for me, it's support wasn't
Just in case this wasn't apparent, you certainly *can* use psycopg2's
bindings when you're in an otherwise SQLAlchemy app. Worst case you can
retrieve a raw psycopg2 connection using connection.raw_connection and do
whatever you need. If you truly have some use for LOBs, SQLAlchemy isn't
