List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:January 28 2009 10:04pm
Subject:Re: SSQLS structure problem with sql_tinyint_unsigned and mysqlpp::Null
View as plain text  
On Jan 28, 2009, at 1:20 PM, Edward Diener wrote:

> Is there a better way to fix this problem ?

Probably not without removing at least one conversion ctor or  
conversion operator from MySQL++.  This sort of ambiguous conversion  
mess is just one of the consequences of a static type system that  
allows overloading.  There are simply some sensible things you might  
want to do that have no way of being expressed unambiguously.

The flip side of that coin, of course, is something like Perl, so  
flexible about conversions that you can easily lose data if you're not  
careful.

You're welcome to dig into the sources to see if you can find the  
conversion method that isn't pulling its own weight, and we can talk  
about a v4 Wishlist item to remove it.  Or, you can hack it out of  
your own copy.
Thread
SSQLS structure problem with sql_tinyint_unsigned and mysqlpp::NullEdward Diener28 Jan
  • Re: SSQLS structure problem with sql_tinyint_unsigned and mysqlpp::NullWarren Young28 Jan
Re: SSQLS structure problem with sql_tinyint_unsigned and mysqlpp::NullEdward Diener29 Jan
  • Re: SSQLS structure problem with sql_tinyint_unsigned and mysqlpp::NullWarren Young29 Jan
    • Re: SSQLS structure problem with sql_tinyint_unsigned and mysqlpp::NullWarren Young3 Feb