Re: SSQLSv2 design discussion
Joel Fielder wrote:
> 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).
Perhaps you are overengineering it. What's wrong with just subclassing
mysqlpp::Date and telling ssqlsxlat to use your subclass? Every
assignment to it can run the text through your extra logic.
--
MySQL++ Mailing List
For list archives:
http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsub=lists@pantek.com
Received on Thu Aug 16 13:29:12 2007
This archive was generated by hypermail 2.1.8
: Sun Oct 07 2007 - 10:03:03 EDT
|