On Tue, Jul 21, 2009 at 20:20, rb<[email protected]> wrote: > > A design choice? Does this mean that there is no will/interest to add > indices to the DAL now or forever? How about table (multi-column) > constraints? Can these be added without the exponential increase in > complexity?
As far as I can tell, this is not something that will never be done as long it will fit in the overall web2py picture. If you have a good idea, we can allways have a look at it. Web2py is focused on webdevelopement, not so much on tuning the db. There are better tools for that (and you can do the executesql). Multi column constraints is tight much closer to data entry, so is more likely to be added (but that is just me). > One last thought on indices. The primary key of a table is > automatically indexed I believe. For DAL/Web2py tables this refers to > the 'id' field. Most often however, this id field is not the intended > primary key - the intended primary key is the columns that make up the > unique signature used to fuse the attributes (non-key fields) > together. Thus running tables without indexing the (intended) primary > key greatly slows down queries, no? Depends on several factors, including volume. Also non-key fields might need indexing when they are frequently being used for searching. > And if the DAL leaves the user to define indices outside of the DAL > then must the user also turn off migration ? Massimo advices that for production migration should be kept off (unless upgrading via web2py) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
