I'm on top of this "issue" in these days, but in the end we will just have
to create yet another adapter (maybe a mssql*u* , mssql3*u* and mssql4*u*).
The problem is subtle, and goes pretty unnoticed.
If - as I - you create an app with mssql: (or mssql3, or mssql4) which have
"varchar" type the o
yes but be aware this will affect all the applications. not just this one.
On Wednesday, 15 April 2015 02:43:48 UTC-5, Paolo Valleri wrote:
>
> mssql adapters are quite messy.
> MSSQL2Adapter is the adapter that uses 'nvarchar' as type, however it
> inherits from MSSQLAdapter, given that it doesn
mssql adapters are quite messy.
MSSQL2Adapter is the adapter that uses 'nvarchar' as type, however it
inherits from MSSQLAdapter, given that it doesn't have the features of
MSSQL4Adapter.
For backward compatibility I don't think MSSQL2Adapter will be never
updated to inherits from MSSQL4Adapter.
3 matches
Mail list logo
