Re: Using OneToOneField in reverse from values or values_list is rejected with "Invalid field name" (repost)

On Apr 7, 10:47 am, Julien Phalip wrote: > Hi Matt, > > Do you think this could be related > tohttp://code.djangoproject.com/ticket/11448 > ? > > If so, do the patches attached to that ticket help resolve your issue? > > Thanks, > > Julien Hi Julien, Thanks for your reply

Re: Using OneToOneField in reverse from values or values_list is rejected with "Invalid field name" (repost)

On Apr 7, 8:59 am, Russell Keith-Magee wrote: > > I'd need to go spelunking through the code to be sure, but if this is > happening, I'd be guessing it's oversight. From a quick scan of the > test suite, I can't find an obvious test for values() on one-to-one > fields.

Re: Using OneToOneField in reverse from values or values_list is rejected with "Invalid field name" (repost)

On Apr 6, 12:09 am, Matt Hoskins wrote: > My apologies for reposting this - I originally posted this at the end > of January and as soon as I posted it I realised that with the push > for bug squashing for the 1.3 release going on I probably wouldn't get > any attention

Re: Using OneToOneField in reverse from values or values_list is rejected with "Invalid field name" (repost)

On Tue, Apr 5, 2011 at 10:09 PM, Matt Hoskins wrote: > My apologies for reposting this - I originally posted this at the end > of January and as soon as I posted it I realised that with the push > for bug squashing for the 1.3 release going on I probably wouldn't get >

Using OneToOneField in reverse from values or values_list is rejected with "Invalid field name" (repost)

My apologies for reposting this - I originally posted this at the end of January and as soon as I posted it I realised that with the push for bug squashing for the 1.3 release going on I probably wouldn't get any attention (and thus comment or replies :), so I'm trying a repost now that 1.3 is