from curiousity, I just read thru the lib docs, and the module source (./Lib/decimal.py)... It seems like mapping the various DB's rules (for example, see the allowed conversions chart from T-SQL here: http://msdn.microsoft.com/en-us/library/ms187928.aspx) ... and then running the doctests that do exist for decimal.py, but against values retrieved from each of the backend / decimal storages will probably be a good thing to do.
Reading the python docs, it will also be interesting to see how people deal with actually using this (I know people want to - I wonder what it will really take the application writer to make this shift.... maybe it will be ok.) This seems like an undertaking that - by it nature - calls for care... Ok - back to trying to "enjoy" the weekend (by doing chores around the house?!!! ;-) - Yarko On Sun, May 24, 2009 at 10:16 AM, dlypka <dly...@gmail.com> wrote: > > I wish it were so easy to deal with Microsoft... > > On May 24, 10:50 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > Can you help me on this by providing an example of decimal statement > > in create table for each of the supported databases? > > > > Massimo > > > > On May 24, 5:07 am, "Francois (Jersey)" > > > > > > > > <francois.ches...@googlemail.com> wrote: > > > Floats can not be used, as float may give a different result from > > > decimal, and this is not acceptable for financial applications: > > > An explanation of the difference can be found athttp:// > docs.python.org/library/decimal.html > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
