Re: CLOB Problem with DBD::ODBC/DBD::ADO for SQL Server

Mickautsch, Alfred wrote:
-----Ursprüngliche Nachricht-----
Von: Martin Evans [mailto:martin.evans@xxxxxxxxxxxx]
Gesendet: Dienstag, 30. Januar 2007 12:40
An: dbi-users@xxxxxxxx
Betreff: Re: AW: AW: Re: AW: CLOB Problem with DBD::ODBC/DBD::ADO for
SQL Server
[...]
I insert 24 chars (16 \ and 8 line feeds) and I get back 24 chrs.

I am unsure why the code does not insert CR\LF as I am 100% sure the file itself contains CR\LF.

I have tried with ntext, text and char fields - no difference.

I have run it through a tds spy and can see the line feeds going through fine in both directions.
[...]

Yes, it is a weird problem. There seems to be a byte count limit under which this effect does not occur. It happens with my text example of 102858 bytes. With a text of 569 bytes it does not seem to happen. It is very confusing.

Thank you for your efforts.

Servus -- Alfred

As you indicate, the length has something to do with it. At 24000 chrs it works and at 48000 chrs you lose each \ followed by a <linefeed>. It is of no consolation to you but I have duplicated it with the MS SQL Server driver and also demonstrated it works fine with our sql server driver. There is a difference. The MS SQL Server driver execs sp_execute to do the insert with the literal text whilst our driver calls sp_execute with a parameter.

I had thought turning off translation might help but it doesn't.

I am of the opinion this may be a ms sql server odbc driver bug in which your options are limited unless you have a support contract or can come up with a workaround.

Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
.

Relevant Pages

  • MSSQL Server ODBC driver crash
    ... If the SQL Server driver's option "Use ANSI nulls, paddings and warnings" ... is not set and the length of char is over 623, MS SQL Server driver will ...
    (microsoft.public.data.odbc)
  • MS SQL Server 2000 ODBC driver crash
    ... If the SQL Server driver's option "Use ANSI nulls, paddings and warnings" ... is not set and the length of char is over 623, MS SQL Server driver will ...
    (microsoft.public.data.odbc)
  • Linked Tables - ODBC SQL Server Driver Timeout Expired
    ... SQL Server 2005 back-end with a named ... I need to use the SQL Server driver instead of the Native Client driver when ... first attempt to open one of these linked tables, I get the SQL Server Driver ... perhaps in a table linking code? ...
    (microsoft.public.sqlserver.odbc)
  • Re: Old SQL ODBC driver on 2003 Server
    ... Try installing the latest MDAC ... > I have a Windows 2003 Server which has a very old sql Server ODBC Driver ... If I go into Data Sources and view the SQL Server driver it is ...
    (microsoft.public.sqlserver.odbc)
  • data from access form to stored procedure
    ... I'm unsure how to go about this.. ... I also have a stored procedure that needs to use ... txtbox of the access form to the stored procedure thats running on sql ... (sql server 2000 backend, access 2003 frontend) ...
    (microsoft.public.access.forms)