I find this interesting too since the use of numeric instead of a float is the right decision most of the time.
If you're dealing with money at all - you absolutely cannot use float, you *must* use fixed decimal types or you risk getting into all kinds of really terrible rounding errors. I'm frankly surprised that a scientific computing app is using float with any degree of success. Obligatory link to a reference : http://docs.sun.com/source/806%2D3568/ncg%5Fgoldberg.html The long running transaction support discussed in point #1 will fail if data is modified between loading the initial page on GET and submitting data on the POST. A simple SELECT FOR UPDATE doesn't solve this problem at all, you actually need a full blown unit of work pattern implemented on the server side that ties to your session. vic Using floating point math is well On 11/28/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 11/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Thus, the absence (or different meaning) of table inheritance and > > FloatField made the choice of TurboGears over Django for our > > project. > > Hey V. Chukharev, > > Thanks for this detailed critique, and good luck with your project! > Everybody has different needs, and we can't meet all of them all of > the time. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com > > > > -- "Never attribute to malice that which can be adequately explained by stupidity." - Hanlon's Razor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
