Randy Syring wrote:
> I have searched the list and have seen some examples with Oracle and I
> have seen some examples with MSSQL using 'exec' but without
> parameters. So, I was hoping that someone could give me or point me
> to an example of using a MSSQL stored procedure with both input and
>
John Hampton wrote:
> So, the problem that I am having is that when I try to do a query, I get
> back the following error:
>
> sqlalchemy.exc.ProgrammingError: (ProgrammingError) ('The SQL contains 0
> parameter markers, but 1 parameters were supplied', 'HY000'
So, the problem that I am having is that when I try to do a query, I get
back the following error:
sqlalchemy.exc.ProgrammingError: (ProgrammingError) ('The SQL contains 0
parameter markers, but 1 parameters were supplied', 'HY000')
Yet, in the query output, it is clear that there is a value sup
Rick Morrison wrote:
> > The first step here is to get a full binary round trip working with
> > only pyodbc, no SQLA in use.
>
> Well, that's how I got as far as I did, but that was with straight text,
> no bind params
I did a little more digging into this and found out that pyodbc with
str
Michael Bayer wrote:
> SQLA doesn't quote bind values. It passes bind parameters, so this is
> likely pyodbc assigning quoting.
>
> The first step here is to get a full binary round trip working with
> only pyodbc, no SQLA in use. The dialect can then be adjusted to do
> whatever is neede
John Hampton wrote:
> This is the same conclusion that I had while talking with Mike on IRC.
> Mike believes that there are others out there that use MSSQL and
> SQLAlchemy that have BINARY columns working fine. I was hoping that
> this is true and someone who has had success co
Rick Morrison wrote:
> Hmmm, looks to me as if SQLA is generating the query correctly, but that
> the DBAPI passes along the Binary() value encoded in a Python binary
> string, which MSSQL then interprets as Varchar, and then complains that
> it can't do an implicit conversion. That's a surpris
Rick Morrison wrote:
> Is the column you're having issues with really a VARCHAR, or is the
> message misleading? How did you create the table, pre-existing or via
> SQLAlchemy? Can you show the schema and the code you're trying to access
> it with?
It's a preexisting table. The column in the
I have a similar problem to Sam as shown in the following thread:
http://groups.google.com/group/sqlalchemy/browse_thread/thread/3be1df474de602d0
I get the same error regarding conversion of VARCHAR to BINARY. The
difference is that I am using pyodbc and unixODBC instead of pymssql.
Is anyone
