About a million years ago, when I did DB2 programming, we used DECIMAL a lot. Anything that handled money was a DECIMAL value. We also did calculations on columns, like SUM(). I think it is worthwhile pursuing a solution for the DAL in web2py, as we used it a lot for anything financial. In fact, it was relatively rare that we needed floats or doubles.
Another thread touched on the topic of making the DAL itself somewhat modular. The context of the request was to make DAL more tuned to the needs of GAE developers by exploiting its not-quite-relational feature set. Perhaps these cases could point to a way to modularize the DAL such that it becomes an extendable component instead of a fixed one. In my own case, I have interest in substituting an OODB (developed in- house) for the SQL features of the DAL. Our OODB is really nothing like a relational database, but stores and retrieves objects based on their metadata. Replacing the web2py DAL with my own is beyond my meager ability at this point, but if the DAL itself had a clear interface with web2py I might be able to tackle it. Warm regards, Joe Barnhart On May 24, 6:01 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > *sigh* .... yes, I am coming around to this simple awareness... and there > appears to be no unified decimal approach to sqlite (from what I can > tell).... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
