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?
Yes, I'll add indices outside of the DAL. This thread began because I didn't think that multi-column primary keyed table could perform a get- next-record, but I think I know now how this can be done. 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? And if the DAL leaves the user to define indices outside of the DAL then must the user also turn off migration ? -- Rb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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 -~----------~----~----~----~------~----~------~--~---
