Home/ Questions/Q 3932356
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T23:26:58+00:00

I am using the libodbc++ ODBC wrapper for C++, designed similar to JDBC. I

  • 0

I am using the libodbc++ ODBC wrapper for C++, designed similar to JDBC. I have a prepared statement "INSERT INTO t1 (col1) VALUES (?)", where t1.col1 is defined as VARCHAR(500).

When I call statement->setString(1, s), the value of s is truncated to 255. I suspect the libodbc++ library, but as I am not very familiar with ODBC I’d like to be sure that the wrapper doesn’t just expose a restriction of the underlying ODBC. The ODBC API reference is too complicated to be skimmed quickly and frankly I really don’t want to do that, so pardon me for asking a basic question.

NOTE: an un-prepared and un-parameterized insert statement via the same library inserts a long value ok, so it isn’t a problem of the MySql DB.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t know libodbc++, but PreparedStatements available via ODBC API can store more characters. I use it with Delphi/Kylix ODBC wrapper.

    Maybe there is some configuration in libodbc++ to set value length limit? I have such setting in my Delphi library. If you use PreparedStatement then you can allocate big chunk of memory, divide it into fields and show ODBC where block for each column starts and how long is it via SQLBindParameter() function.

    • 0