From: Date: August 15 2007 12:17pm
Subject: RE: SSQLSv2 design discussion
List-Archive: http://lists.mysql.com/plusplus/6938
Message-Id: <093501c7df25$73a3d810$0400a8c0@joel>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Sorry, I wasn't actually particularly clear with the whole transform
thing - it would need to be possible either at field level *or* object
level.  LocaliseDate would therefore need std::string
operator()(mysqlpp::Date& date) to be applied to each date field as it's
bunged into the SSQLS, whereas an object transformer would have SQLStock
operator()(mysqlpp::Row& row).

For field level transforms, it might also be useful to have a
std::string operator()(mysqlpp::Date& date, mysqlpp::Row& row) variant
as well, just in case the transform depends on other things in the
result set e.g row['timezone'].

Hope that makes sense.

Joel