[sqlalchemy] Re: PyODBCConnector, possible wrong assumption re Unicode in bind parameters

2011-09-12 Thread Victor Olex
I confirm successful build and run time on both 64-bit and 32-bit Linux (RHEL5) againt SQL Server 2008. It has turned out that Pyodbc needed the CPLUS_INCLUDE_PATH set to where my version of UnixODBC was prefixed to prior to building. Best bet is to remove all prior versions including distro

Re: [sqlalchemy] Re: PyODBCConnector, possible wrong assumption re Unicode in bind parameters

2011-09-12 Thread Michael Bayer
On the fedora VM i tried, I fully de-installed the UnixODBC RPMS, so the one built from source should be the only one present. Will take a look at the pyodbc files.. On Sep 12, 2011, at 3:27 PM, Victor Olex wrote: I confirm successful build and run time on both 64-bit and 32-bit Linux

[sqlalchemy] Having problem with constructing update ...from... with sqlalchemy

2011-09-12 Thread Geo
I have a tested update ... from.. statement, like so: update distributors set lead_bonus = lead_bonus + a.sum_amt from ( select target_member as id, sum(amount) as sum_amt from bonus_gen_history where bonus_type=2 and sub_type=1 and source_member in (select

Re: [sqlalchemy] Having problem with constructing update ...from... with sqlalchemy

2011-09-12 Thread Michael Bayer
On Sep 12, 2011, at 5:50 PM, Geo wrote: I have a tested update ... from.. statement, like so: UPDATE...FROM syntax, which is non-standard, isn't built into SQLAlchemy right now. You'd need to either convert this to use a correlated SELECT in the WHERE clause, stick to the SQL string, or

Re: [sqlalchemy] Having problem with constructing update ...from... with sqlalchemy

2011-09-12 Thread george hu
Thanks Michael, that solves my problem. On Mon, Sep 12, 2011 at 3:18 PM, Michael Bayer mike...@zzzcomputing.comwrote: On Sep 12, 2011, at 5:50 PM, Geo wrote: I have a tested update ... from.. statement, like so: UPDATE...FROM syntax, which is non-standard, isn't built into SQLAlchemy