I put a rework of the code posted by Bo into a package
https://pypi.python.org/pypi/vertica-sqlalchemy/0.1
Selects, joins, table introspection works. Let me know if you can use it.
Does anyone have an email for Bo so I can attribute him and check the
license?
thanks,
James
On Saturday, 16
Hi,
I'm using sqlalchemy to generate a query that returns lots of data.
The trouble is, when calling query.execute() instead of returning
the resultproxy straight away and allowing me to fetch data as I would
like, query.execute blocks and the memory usage grows to gigabytes
before getting killed
On Nov 18, 3:01 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On Nov 18, 2009, at 9:57 AM, James Casbon wrote:
Hi,
I'm using sqlalchemy to generate a query that returns lots of data.
The trouble is, when calling query.execute() instead of returning
the resultproxy straight away
Hi All,
I am seeing something I didn't expect using in_.
Here is a simple example, exactly as I expect:
In [13]: col = Trade.c.TradeId.in_([1,2])
In [14]: sel = select([col])
In [15]: print col
Trade.TradeId IN (?, ?)
In [16]: print sel
SELECT Trade.TradeId IN (?, ?) AS anon_1
FROM Trade
Ah, thanks.
Should have searched the bug reports as well as the list.
On Jun 12, 3:27 pm, Michael Bayer [EMAIL PROTECTED] wrote:
this is ticket #1074. A slightly klunky workaround for now is:
col = t1.c.c1.in_([select([t1.c.c1]).as_scalar()])
On Jun 12, 2008, at 10:04 AM, casbon wrote
