I saw your other thread, and it looks very interesting. The downside from my point of view is that I want to easily add new methods, and I'm not sure that adding a table per method would be practical. OTOH, I *am* looking for innovative ideas, which yours certainly is, so I'll be following that thread with interest.
On Jun 16, 8:24 am, DenesL <denes1...@yahoo.ca> wrote: > I was thinking about a more general approach where 'info' can be a > bunch of fields (like an address with city, state, country, > postalcode, ...) and then I would take advantage of web2py's SQLFORM > or FORM to process it. > > My current model has the same 'person' table but 'method' includes the > tablename (e.g. 'address') where the info should be placed, and in > table 'contact' instead of 'info' I store the id of the entry made in > the 'address' table. > > Creating the form(s) to handle this is another story, currently > developing in a separate post. > It will probably need some ajax. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
