[EMAIL PROTECTED] wrote:
DBD::Sybase will support whatever the underlying client libs are capable of
handling.
I'll throw the wrench in now: I'm using the DBD::Sybase bulk copy
interface as well. That's working great but I'm getting a failure
on a table that has a varchar(max) column. I haven't isolated it to
that yet -- I'm going to test with and without that. In the meantime,
if you have any knowledge to bestow on me regarding varchar(max) and
bulk copies, let me know.
This is a RH Linux environment, FreeTDS drivers. Perl 5.8.7,
DBD::Sybase 1.07. Target database is MS SQL Server 9.0.2047.
Bulk loading rocks by the way Michael. ;-)
Michael
Extranet
[EMAIL PROTECTED] - 21/08/2006 15:27
To: fumiakiy
cc: dbi-users
Subject: Re: "max" datatypes support of SQL Server 2005 for DBD-ODBC
Fumiaki Yoshimatsu wrote:
I had a need to support [n]varchar(max) and varbinary(max) datatypes of
MS SQL Server 2005, and patched DBD-ODBC.
Below is the diff from the current svn.
Does anyone know what, if any, support for these DBD::Sybase has?
--
Steve Sapovits [EMAIL PROTECTED]
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
--
Steve Sapovits [EMAIL PROTECTED]