Re: inner join operation on legacy tables?

On Apr 6, 7:26 pm, "jani.mono...@gmail.com" wrote: > > The generated model from inspectdb is only a best guess, but there's > > nothing to stop you editing it. If your field really is a foreign key, > > Not really a foreign key,both tables have a string field ID which is >

Re: inner join operation on legacy tables?

I have eventually made a MySQL view combining the two tables and then used a simple Django queryset on it, but I'd still be curios if there's a Django way of addressing this and similar issues. On Apr 6, 9:26 pm, "jani.mono...@gmail.com" wrote: > > The generated model

Re: inner join operation on legacy tables?

> The generated model from inspectdb is only a best guess, but there's > nothing to stop you editing it. If your field really is a foreign key, Not really a foreign key,both tables have a string field ID which is the same, and unique in one table. So it could be a foreign key except it is not

Re: inner join operation on legacy tables?

On Apr 6, 5:26 pm, Jani Monoses wrote: > Hello, > > what is the most straightforward way of making an implicit joining of > two tables in the Django development version? > > The tables are created by another application and are only read in > Django, and while they have a

inner join operation on legacy tables?

Hello, what is the most straightforward way of making an implicit joining of two tables in the Django development version? The tables are created by another application and are only read in Django, and while they have a field that they can be joined on (a string) that is not explicit in the