------_=_NextPart_001_01C6CDF9.71AFBD32
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

While searching for an example of using ssql with blob data, I came
across the following thread:
http://lists.mysql.com/plusplus/5208

Since the nature of my data could potentially lead me to the same
problem, I'm wondering if this issue has been fixed.=20
I took a look through the change log, but didn't notice a particular
reference to this problem, though that doesn't necessarily mean that it
wasn't there.=20

IF this is still an outstanding problem, what are my options? I'm new to
mysql++, and the only example from the documentation that I found was to
use a query object explicitly, and call row.raw_data(). Are there other
options? (preferably ones that allow me to still use ssqls) Any help
would be appreciated.=20
Thanks,=20
Andy Troutman

------_=_NextPart_001_01C6CDF9.71AFBD32--

Troutman, Andrew T CIV NAVAIR wrote:
The Changelog would say so if it had been fixed.

a) fix it yourself and send in the patch
b) wait for someone else to get around to fixing it; in the meantime,
don't use SSQLS to access blobs

If you're tempted to go for option B, beware that there are several
other pitfalls with blobs right now. This isn't one problem, it's a
whole family of problems with a common root. See the Wishlist in the
svn repo for my current thoughts on how to fix this. If you plan on
tackling the problem, let me know, because it's going to be a lot of
effort to fix it, and I'd hate there to be duplicate work going on.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw