this would even be easier (and correcter if the terms contain %)
written as:
cond = or_(*[Fruit.name.contains(term) for term in terms])
On 8 mei, 21:59, Kyle Schaffrick k...@raidi.us wrote:
On Fri, 8 May 2009 12:52:09 -0700 (PDT)
Bryan bryanv...@gmail.com wrote:
I can't figure out a
Could this be related to this change:
http://www.sqlalchemy.org/trac/changeset/5564
I encountered a similar problem with mssql/pyodbc today (the echo
output showed the correct statements and params, but no changes seemed
to be made in the db at all). The problem only occurred when using the
Oops, make that:
MSSQLDialect.do_begin = lambda self, conn: None
(pass is not allowed in lambda statements ;-) I had already corrected
the mistake in my code, only to make it again posting the message,
sorry...)
On 27 apr, 22:33, polaar steven.vereec...@gmail.com wrote:
Could this be related
I've just noticed a remaining problem with the pyodbc/inserts with
triggers/scope_identity()/set nocount on/nextset() thing ;-) (it's
still a workaround if I understand correctly?)
If nocount is off (eg. turned off again by the trigger as it seems in
my case), MSSQLDialect_pyodbc.do_execute jumps
.
Rick
On 3/14/07, polaar [EMAIL PROTECTED] wrote:
{'pyodbc': use_pyodbc, 'adodbapi': use_adodbapi, 'pyodbc':
use_pyodbc}.get(module.__name__, use_default)()
Sorry, should be pymssql instead of pyodbc twice, but I guess you got
On 12 mrt, 21:47, polaar [EMAIL PROTECTED] wrote:
FYI, specifying module=pyodbc didn't seem to help wrt the
ConcurrentModificationError. Didn't have very much time, had a (very)
quick look at the code in mssql.py, and at first sight, it would seem
that sane_rowcount is a global variable
adodbapi
(or pymssql) installed in order to use pyodbc correctly???
On 9 mrt, 23:29, polaar [EMAIL PROTECTED] wrote:
Yes, but I'm starting to think I'm doing something wrong ;-) I suppose
I should call create_engine with the module=pyodbc?
I was just using the creator argument (as I was doing
, polaar [EMAIL PROTECTED] wrote:
On Mar 7, 3:29 pm, Tim Golden [EMAIL PROTECTED] wrote:
code
from sqlalchemy import *
metadata = BoundMetaData (mssql://VODEV1/TimHolding)
test = Table (test, metadata, autoload=True)
result = test.insert ().execute (code = ABC)
print
On Mar 7, 3:29 pm, Tim Golden [EMAIL PROTECTED] wrote:
code
from sqlalchemy import *
metadata = BoundMetaData (mssql://VODEV1/TimHolding)
test = Table (test, metadata, autoload=True)
result = test.insert ().execute (code = ABC)
print result.last_inserted_ids ()
# = [1]
/code
which is
Hi,
I recently tried out sqlalchemy with mssql via pyodbc (after being
bitten by the adodbapi bug with the truncated parameters), and noticed
the following problem:
On inserting records into tables with triggers, pyodbc fails on the
'select @@identity as lastrowid' statement with an 'invalid
10 matches
Mail list logo
