What is the actual reson this limitation exists? I'm trying to migrate from SQLServer to SapDB for another project here at work and this is as far as I got.

The background is that we have some XML data that goes in a "long varchar" column (the documents can be quite big) and inserting the data works fine. However, when I try to change the contents I get this error.

We are using ODBC from C++ to accomplish this. I suppose that perhaps using Recordset objects will work around this but the problem is that that would cause a lot of code to have to be changed. Changing the SQL statements is OK, but not using a completely different method of writing the data.

As far as I can tell, the only workaround is to remove the old row and create a new one, but is there really no better way? Perhaps someone can enlighten me as to why the limitation exists in the first place?

Thanks in advance

Elias M�rtenson



_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to