handling unicode data

[Filipe]

> In summary
>
> + Depends on what your requirements are, but...
>
> + Go for ADODBAPI for the widest spread of versions and licenses, but
> the least cross-platformability
> + Go for Object Craft MSSQL for <= 2.3 and best overall behaviour
> + Go for pymssql for >= 2.4 with some small limitations
> + Go for mxODBC for general purpose databasing, cross-platform, but
> without .nextset and possibly Commercial licensing
> + If all else fails, and you've got the SQL Server command line tools,
> use the ASPN Recipe
>

Very nice review! Not having a commercial license ir really a "must"
right now, and I'd really prefer it being cross-platform, so I think
pymssql might not be a bad choice after all. If I can't make unicode
data work in a reasonable way I'll probably switch to ADODBAPI, or
maybe the odbc module that comes with PyWin32 mentioned by Frank.

thanks,
Filipe