Hi,
I've go a report of a problem with Microsoft SQL Server 9.0: I've a
SQLObject database structure which uses a number of UnicodeCol
columns without length limit.
In other database servers - MySQL, PostgreSQL, ... - these
columns are correctly mapped to TEXT types, while in SQL Server
a VARCHAR(4000) is used.
Looks like this choice is forced in the SOStringLikeCol._mssqlType()
method, in the col.py file.
My questions are:
1. why this choice?
Performances, I assume, but it seems a bit rude to me: I expected
to get an unlimited field.
2. any work-around?
Modifying SQLObject is not an option: mine is a free software
application, and I have no control of the installation base.
Thanks!
--
Davide Alberani <davide.alberani _at_ gmail.com> [PGP KeyID: 0x465BFD47]
http://erlug.linux.it/~da/ <http://erlug.linux.it/%7Eda/>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
