Hi,
While building a blog type application, I seem to have stumbled upon a
bug. In a nut shell all object attributes have become read only when I
fetch the object from a query set which is fetched using the xxx_set()
API.
Please see the pdb trace for details. I have added comments to depict
th
Hi,
While building a blog type application, I seem to have stumbled upon a
bug. In a nut shell all object attributes have become read only when I
fetch the object from a query set which is fetched using the xxx_set()
API.
Please see the pdb trace for details. I have added comments to depict
the
> While building a blog type application, I seem to have stumbled upon a
> bug. In a nut shell all object attributes have become read only when I
> fetch the object from a query set which is fetched using the xxx_set()
> API.
Hi Chirayu,
Looks like the problem is not the FOO_set() manager, but s
> While building a blog type application, I seem to have stumbled upon a
> bug. In a nut shell all object attributes have become read only when I
> fetch the object from a query set which is fetched using the xxx_set()
> API.
Hi Chirayu,
Looks like the problem is not the FOO_set() manager, but s
Chirayu Patel wrote:
> Hi,
>
> While building a blog type application, I seem to have stumbled upon a
> bug. In a nut shell all object attributes have become read only when I
> fetch the object from a query set which is fetched using the xxx_set()
> API.
>
> Please see the pdb trace for detail
>
> A little weird, maybe someone else can explain exactly what's going
> on. Presumably a QuerySet slice is somehow not being treated as the
> object itself.
Hi,
As Eric correctly pointed out that slicing a QuerySet is not "sticky".
Whenever you take a slice of an exisiting QuerySet, Django clo
6 matches
Mail list logo
