On Tue, Jul 21, 2009 at 07:49, rb<[email protected]> wrote: > I do have a point: the DAL does not seem to > support multi-column keys. It also does not support multi-column > constraints.
DAL itself does not yet support this, however you can always execute SQL directly to apply these constraints on DB level. > I'm curious why. Is this something that's just not done yet or is it > something for which there has been no need or is it something the > developers don't want to do for some reason? So far it is not done yet, I don;t know yet if the new DAL wil support it, but it is an area we need to look into. > The answer of "don't use > the DAL" is kinda missing the point. I ***want*** to use the DAL. That's fine. But as the DAL currently has some limitations you have to work within it. As indicated, the DAL is currently being rewritten - or at the least the specs are. > Further, I ***can*** just add a 'orderby' clause to the select() > function but this is expensive. Correct me if I'm wrong but I believe > that a table's primary key is automatically indexed. When selecting on > the primary key the db automatically uses its index - which speeds > things up quite a bit. Adding indices to much-used queries can really > speed things up. So if I cannot use indices in the DAL ***and*** I > cannot have my primary key indexed then _sigh_ isn't there room for > improvement here? You can always add indices to the table, but that is something that cannot be directly done (currently) via the DAL, you have to execute the SQL to create them manually (DAL does support to run direct SQL when needed) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
