Are you sure they REALLY have to be in two separate tables and not just one (optionally with a recursive join to support parent-child relation) ?
-- Luc. On Sunday, 14 April 2013 03:38:51 UTC+1, lucas wrote: > > ok, i need some opinions on how to do this best and how to implement the > best method. > > consider payments. a table named "firms" that can make payments and > multiple logins under auth_user. a second table of auth_user that can make > payments and obviously by definition a single login under the same table > name. a third table named "payments" that for each record that can either > reference the id under auth_user for the single independent login user OR > the id under firms for the relational list of users. > > how can i setup relational fields in payments that can either reference > the auth_user table id OR the firms table id? > > thanx in advance. lucas > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
