From: Kevin Regan
Date: June 15 2009 9:12pm
Subject: Using mysqlpp::quote on a std::ostringstream?
List-Archive: http://lists.mysql.com/plusplus/8631
Message-Id: <4B18A8F75A6384449755BC7784073E9360CEBD74E2@exch11.olympus.f5net.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="_000_4B18A8F75A6384449755BC7784073E9360CEBD74E2exch11olympus_"

--_000_4B18A8F75A6384449755BC7784073E9360CEBD74E2exch11olympus_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Looking through my code (written by someone else), I'm seeing that we are u=
sing a std::ostringstream to build up arguments to a stored procedure.  We =
than call "str()" on that stream and insert the results into a query object=
.  We do this because we want to allow the arguments to be set before we ac=
tually create the Connection or Query objects.

We are using the "mysqlpp::quote" mechanism when inserting strings into the=
 std::ostringstream.  This worked with 2.x, but not for 3.x (the strings ar=
e not quoted).  Looking through manip.cpp, it looks like this is documented=
 as not being a supported action (although there is some code that attempts=
 to do the right thing anyway).

I'm guessing that we were just using an unsupported mechanism that no longe=
r works the way we wanted it to.  Is this correct?

Can anyone recommend an alternate approach?  The idea would be to be able t=
o set the arguments (of various types) before the Connection or Query objec=
ts are created.

Sincerely,
Kevin Regan
F5 Networks


--_000_4B18A8F75A6384449755BC7784073E9360CEBD74E2exch11olympus_--