ntext - sql server
In SQL Server 2012, the ntext has been deprecated; however, for sql alchemy 0.9.4 for p2.7, it still uses the ntext in the mssql dialects which causes issues/sql type errors. Found solution in C:\Python2732\Lib\site-packages\sqlalchemy-0.9.4-py2.7.egg\sqlalchemy\dialects\mssql\base.py and replacing references to nvarchar.
Comments (7)
-
repo owner -
repo owner - changed milestone to 0.9.5
-
reporter http://technet.microsoft.com/en-us/library/ms187993.aspx
nvarchar is a variable length type
-
repo owner OK so this is TEXT also and they want to use varchar(max).
However, this means that the Text()/ UnicodeText() types just shouldn't be used with SQL Server. You can instead use String()/Unicode(), which will render as "varchar(max)" / "nvarchar(max)" right now if you don't give them a length.
As it stands, changing Text/UnicodeText to spit out (n)varchar(max) seems like it would be pretty backwards incompatible/surprising for existing users.
-
repo owner - attached 3039.patch
this is going to surprise people so it'll be for 1.0
-
repo owner -
repo owner - changed status to resolved
- SQL Server 2012 now recommends VARCHAR(max), NVARCHAR(max),
VARBINARY(max) for large text/binary types. The MSSQL dialect will
now respect this based on version detection, as well as the new
deprecate_large_types
flag. fixes#3039
→ <<cset c8817e608788>>
- Log in to comment
what type does SQL Server 2012 offer for arbitrarily large text that is unicode ? NVARCHAR is a fixed size; unless SQL Server 2012 allows arbitrary-sized NVARCHAR that's not an option.