> Thanks for the hint. I run maxdb 7.5.0.16 but the python modules seem
> to be different from these ones. At least dbapy.py is different, with
> it's paramstyle as qmark now. Aaarrgh !
Named parameters are still allowed, so you can write either
cursor.execute ('select * from whatever where col = ?', [1])
or
cursor.execute ('select * from whatever where col = :value', [1])
But some software thought that named parameters require a dictionary as the second
argument to execute:
cursor.execute ('select * from whatever where col = :value', {'value': 1})
And I can't implement this as I pass the SQL string directly to the database, so I
don't know anything about the names. And unlike Oracle, MaxDB interprets named
parameters as just a different notation for question marks. So having the same name
twice gives two positional parameters, not two references to the same parameter.
Daniel Dittmar
--
Daniel Dittmar
SAP Labs Berlin
[EMAIL PROTECTED]
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
