List:MySQL++« Previous MessageNext Message »
From:Joel Fielder Date:August 15 2007 10:17am
Subject:RE: SSQLSv2 design discussion
View as plain text  
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

Thread
SSQLSv2 design discussionWarren Young15 Aug
  • Re: SSQLSv2 design discussionChris Frey15 Aug
    • Re: SSQLSv2 design discussionWarren Young16 Aug
      • Re: SSQLSv2 design discussionChris Frey16 Aug
  • RE: SSQLSv2 design discussionJoel Fielder15 Aug
    • RE: SSQLSv2 design discussionJoel Fielder15 Aug
      • Re: SSQLSv2 design discussionWarren Young16 Aug
        • RE: SSQLSv2 design discussionJoel Fielder17 Aug
    • Re: SSQLSv2 design discussionWarren Young16 Aug