FreeTDS Development Group

[Michael Peppler <mpeppler AT peppler.org>]

On Thu, 2004-11-04 at 11:25, Thompson, Bill D (London) wrote:
> Michael,
> 
> I don't know if this is what you're after, but I can tell you that
> freetds doesn't have any issues with large (n)(var)char columns per se.
> 
> I've just written a program that selects text from syscomments, which in
> SQL server is NVARCHAR(4000) -
> I'm using db-library, mind.
> 
> I notice stuff in the Sybase open client client-library reference manual
> (12.5) with respect to support for WIDE varchars etc. I don't think we
> have done anything specific to deal with wide columns, but they may just
> work out of the box...

Probably. For Sybase CT-lib it's a capability that is turned on if the
CS_VERSION setting is large enough, and varchar()/varbinary() values
that are wider than 255 are returned as CS_LONG_BINARY and CS_LONG_CHAR.

Still, as far as DBD::Sybase and/or Sybase::CTlib is concerned it just
picks up the size from ct_describe() and goes from there, so as long as
ct_describe() returns reasonable values then it should just work.

> I am keen on getting ct-lib as complete as possible.
> As you may have picked up, we now have the blk library implemented, as
> well as the ct_cursor() functionality, enabling clients to interact with
> server side cursors through the API. I am next looking at ct_dynamic()
> etc.

>From where I sit the ct_dynamic() functionality is the most important
one, as that is used extensively in DBD::Sybase.

I see from your other email that lots of other things have been
implemented, which is really great - thanks a lot!

Michael
-- 
Michael Peppler                              Data Migrations, Inc.
mpeppler AT peppler.org                       http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or 
long term contract positions - http://www.peppler.org/resume.html