Updating a BLOB

  • Thread starter Thread starter Christopher Weaver
  • Start date Start date
C

Christopher Weaver

I'm creating / adding a parameter to an update command with this:

cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("Note",
System.Data.Odbc.OdbcType.Binary, 0, "Note"));

Everything compiles just fine and dandy, and the value of the field "Note"
gets posted as well, just not all of it. I set the length of the field in
the third argument of the Add method to 0 hoping that it would take it to
mean 'whatever it is'. Instead, it's taking some of the data and dumping
the rest. I also tried null and -1. No change. So I tried 5000000, but
the result was the same. In each case it posts the first 80characters to
the backend and dumps the rest.

Here's the biggest clue, the field itself is defined thusly:

"Note" BLOB SUB_TYPE 1 SEGMENT SIZE 80,

So it appears that the inner workings of the DA or DS or whatever, are
taking a cue from the backend and sending only 80 characters. I can and
have put considerably more than 80 in this field using a console tool made
to work with the RDBMS, and my VS 2003 app reads the data and displays it
correctly. But if I modify the field and post it -- it's 1 through 80 and
nothing more that survive.

Any thoughts on how I can get my odbc components to look beyond the segment
size?
 
Never mind!!!

I found the solution. The correct type is Text. It looks like this:

cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("Note",
System.Data.Odbc.OdbcType.Text, 0, "Note"));

I've been able to post hundreds of characters with no problem.
 
Back
Top