It really depends. I find that strings usually work well enough because sorting by string usually will give you the same result as if you sorted by the date, or by the number represented in the string. Obviously it is quite slower. Although you could create an index on the values to make it faster.
For me, the problem with more columns is not the overhead, since with this model you could know the type before you fetched the result. So you could make selects that would only request the column for the specific value type. The only problem I see with having several column fields for the different types is the added code complexity. If you are going to be doing a lot of searching and filtering by these values it may well be worth it. If these values are mostly just for displaying then it isn't. Of course, benchmarking is always a good idea so test your use case. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
