On Wednesday 13 February 2008 17:45:25 Oleg Broytmann wrote: > Yes, but think about (size=5, precision=5). SQLObject doesn't do > a quantization, and SQLite will store "2112.123456789" - it is just > a string - but what about the padding?..
How does the data get marshalled by SQLObject and/or sqlite? The size/precision constraints aren't really enforced by sqlite, are they? Does SQLObject police this? Anyway, if we require that SQLObject work with legacy databases unmanaged by SQLObject, then I doubt that padding will make ORDER BY work right, in general. But if you ask me, having ORDER BY broken is better than having object types broken and potential inaccuracies in data that needs guaranteed accuracy. cs ------------------------------------------------------------------------- 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
