This solution is ok if you do not have too many (<1000) records that can be referenced. It has no problems with referential integrity in the sense a record A may reference a record |5| that does not exist but it does not break the system, it does not show and the broken reference is eliminated automatically if the record is edited in a SQLFORM.
This was implemented exactly for speed reasons (the by the book solution would be to have a many-to-many relation) and in fact you can use it on google App Engine which does not supports joins. Massimo On Apr 24, 9:22 am, dvid <[email protected]> wrote: > I know, there is a "multiple=True" way to do it, which leads to > representation like |4|5|7| in the textual db field. The solution > seems to be straightforward and there is handy widget to deal with. > > But I am concerned about scalability, performance and referential > integrity. Should I use this for a production site with intense db > query usage? > > The solution with table in the middle would not be so easy to go, but > less proprietary and more proven. > > Thanks for your recommendations... > > David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
