achipa you're right but isn't the second rule of web2py "every table must have a unique id field".
(the first rule of web2py being "you do talk about web2py") On Dec 1, 11:01 am, achipa <[EMAIL PROTECTED]> wrote: > Not sure if it applies here, but you can have multi-column (primary) > keys in some DBMS and that can cause some headache with regard to > id's. > > On Dec 1, 11:11 am, billf <[EMAIL PROTECTED]> wrote: > > > The only reason I can see for allowing references on a field other > > than id is if you are de-normalizing, i.e. duplicating some data from > > a reference table into your primary table to save a join. I'm not > > sure how common this is and I would be tempted to stipulate that the > > reference was still by id (so have both id and duplicated field in > > primary table). > > > Pmate: with respect, how does referencing by id or field affect > > indices in respect of speed and foreign relationship? (apart from if > > the non-id is text it will probably be a little slower). > > > > Should we allow references other than to the id field? > > > On Nov 29, 2:34 pm, pmate <[EMAIL PROTECTED]> wrote: > > > > yes Denesi, that's the point. > > > Usually indexes in a table can be more than one. And they are useful > > > for the speed of queries and for foreign relationship, i think --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
