Hello Michael.
Just a question. When I first posted about my problem of how to connect to MSSQL
from Linux/Debian, you mentioned that you are running similar setup in
production, or at least that is how I understood it. Am I correct? If so, is it
similar to this:
* Connect from Linux/Debian
*
On Oct 10, 2012, at 6:01 AM, Ladislav Lenart wrote:
Hello Michael.
Just a question. When I first posted about my problem of how to connect to
MSSQL
from Linux/Debian, you mentioned that you are running similar setup in
production, or at least that is how I understood it. Am I correct? If
Hello!
I finally managed to solve the problem (with the great help of my colleagues)!
The culprit: python-pyodbc package in Debian/testing is nearly THREE years old
now (version 2.1.7). I removed it and easy-installed the version 3.0.6 which
does not have the encoding bug anymore. Now everything
Hello.
Thank you for the information. I am using freetds 0.91 without issues. But note
that on Debian/testing, the driver file libtdsodbc.so is NOT part of any
freetds-* package. It is part of the package tdsodbc. See my previous e-mail for
detailed installation instructions.
Ladislav Lenart
Python version: 3.2.3
sqlalchemy version: 0.7.9
(Please see the attached source file.) I have a class Simple, which has two
subclasses - MixedFirst and MixedSecond. These two subclasses have a field
in common, namely, mixed. So I have put it in a separate class (a mixin)
named Mixin, which both
This is ticket #2472 and is resolved for 0.8, where this script returns a
column conflict error. The issue is described at
http://docs.sqlalchemy.org/en/latest/orm/extensions/declarative.html#resolving-column-conflicts
and in this case, using 0.8 only, is resolved using this form:
class
I tried the example you showed in the last post and it worked. Thank you so
much!
I know this is a very uncommon use case, so I really appreciate the help.
Thanks again,
Ben
On Tuesday, October 9, 2012 5:26:40 PM UTC-5, Michael Bayer wrote:
On Oct 9, 2012, at 5:42 PM, Michael Bayer wrote:
