On Wed, 2012-02-08 at 12:45 +0530, kenneth gonsalves wrote: > On Tue, 2012-02-07 at 19:29 +1100, Mike Dewhirst wrote: > > On 7/02/2012 6:14pm, kenneth gonsalves wrote: > > > On Tue, 2012-02-07 at 08:06 +0100, Babatunde Akinyanmi wrote: > > >> Perhaps you made a change to a model and forgot to syncdb on your > > >> Fedora 15 machine..... > > > > > > > When you have eliminated all the possibilities what remains must be > > the > > problem :) > > > > The trick is to confirm your assumptions one by one. > > code: all three machines are running code pulled from the same repo. > django version: all three are on r 17461 > database: the table structure on all three is identical. (in fact two > machines have the same data also). Postgresql versions differ, but > this > is a django error - not a database error. > The offending line of code worked fine on the F15 machine when it was > running F14 > Altitude: two of the machines are at 7200 feet above sea level, but > the > offending machine is at 3400 feet.
I finally deleted the whole django-trunk and made a fresh svn checkout. Then it works. Must have been some stale .pyc file or some file got corrupted. -- regards Kenneth Gonsalves -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
