On Thu, Feb 14, 2008 at 05:59:23PM +0300, Oleg Broytmann wrote:
> we are making a workaround for the backend that doesn't have a decimal
> type. But the workaround has a price.
Well, my resolution on the issue is:
DecimalCol will not be changed. I will add documentation explaining the
type affinity problem in SQLite.
There will be a new DecimalStringCol that stores Decimals as text. If
you want quantization please write a validator class, and I will include it
into SQLObject. Initially it will be off, but a user can easily use it
- every column has a "validator" keyword argument.
With all these changes a user is free to choose an implementation and
its price - DecimalCol or DecimalStringCol, or DecimalCol+quantization, or
DecimalStringCol+quantization.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
