Hi Carlos 'Crud' is just a shortcut way of creating simple forms. In production systems we normally create the forms using the more flexible SQLFORM or a lower level method which gives even more flexibility.
With regards your table design, there is nothing wrong with that, it sounds like a very 'normalized' design. In relational DBs you must link the tables using foreign keys. In web2py you can do that when you define the tables using the keyword 'reference'. You can then display the foreign keys in a more meaningful way using 'format='. I am not sure whether this reply has been so helpful, but IMO your best way forward is to read the book and then ask specific questions to the group. Best wishes -David On Nov 17, 3:23 am, Carlos <carlosgali...@gmail.com> wrote: > Hi, > > Does anybody have any recommendations about this?. > > Thanks, > > Carlos > > On Nov 15, 7:23 pm, Carlos <carlosgali...@gmail.com> wrote: > > > Hi, > > > What should I do in order to supportcrudoperations with joined > > tables?. > > > For reference, I have a 'central' table in my design called 'entity' > > which contains lots of data (including names, company, emails, phones, > > address, etc.) and I want many other tables to point to ONE entity > > instance, i.e. 'entity' as an _extension_ of records in many different > > tables. > > > My background is with object databases, and this kind of design makes > > sense, although I'm not sure if it makes sense with relation > > databases?. > > > Thanks, > > > Carlos > >
