Re: Django Generic ForeignKey vs Multiple Foreign Key Fields

2013-04-08 Thread Javier Guerra Giraldez
On Mon, Apr 8, 2013 at 8:43 AM, Javier Guerra Giraldez wrote: > On Mon, Apr 8, 2013 at 5:34 AM, Arun Prabhakar wrote: >> more can come in the future > > that's reason enough to use Generic relations (of course, much better would be if you can refactor your data representation so you can go with

Re: Django Generic ForeignKey vs Multiple Foreign Key Fields

2013-04-08 Thread Javier Guerra Giraldez
On Mon, Apr 8, 2013 at 5:34 AM, Arun Prabhakar wrote: > more can come in the future that's reason enough to use Generic relations -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving ema

Re: Django Generic ForeignKey vs Multiple Foreign Key Fields

2013-04-08 Thread Arun Prabhakar
Hi Martin, A and B are known, and more can come in the future, so it would seem generic is the way to go, but then I dont want to reference on all tables in django. But using the FK has problem of introducing alter tables later. Confused about going with which approach. What do you suggest?

Re: Django Generic ForeignKey vs Multiple Foreign Key Fields

2013-04-08 Thread Martin J. Laubach
It's simply a question of what you want to model. *GenericFK* means for each instance "I have a relationship with some other (undefined) entity". *MultipleFK* means "I have relationships with both well-known entities A and B". Totally different things. Cheers, mjl -- You received