On 4 November 2016 at 18:28, <mich...@zanyblue.com> wrote: > > Unfortunately, the apps are currently in different DB's. > > On Friday, November 4, 2016 at 10:26:34 AM UTC-7, Javier Guerra wrote: >> >> that's what foreign keys are for
even so, a foreign key field is the answer. i see three different ways to do it: - on the app. just add an indexed (unique) field, with the id on the other DB table - with a 'ghotst' table, that is actually related to your Users model and some model methods to manage it - managed by the database itself. not sure about other RDBMS, but postgre at least have some serious "foreign data wrapper" capabilities that make many kinds of other things look like regular tables. [1]: https://wiki.postgresql.org/wiki/Foreign_data_wrappers -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFkDaoRFAOBDC35dOFGWrBfScT%3DRGxH3xGykKQDkhYgnqgT_Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
