Hi,
Not sure how this one slipped through - sorry for replying so late.
This is a regresssion and I have created ticket #575 for this issue.
On 7 Jun 2009, at 13:03, Mohamed Barwani wrote:
> Hello
>
> In my snippets of code that I used to evaluate pyamf 4.0 I did
> something like this with django models;
>
> def my_service(....)
> user = Users.objects.latest('id')
> user.my_extra_attribute = "Something or other"
> return user
>
> And the amf client will see an object with all user fields AND
> my_extra_attribute. However, that doesn't seem to work with 4.2, the
> recent changes are awesome, cause they get all the django related
> fields, so am not reporting any problems here..
>
> My question is how can I get the best of the two worlds? Any
> recommendations?
>
> cheers
> --
> I write for the same reason I breathe - because if I didn't, I would
> die. --Isaac Asimov
> _______________________________________________
> PyAMF users mailing list -
users@...
>
http://lists.pyamf.org/mailman/listinfo/users_______________________________________________
PyAMF users mailing list -
users@...
http://lists.pyamf.org/mailman/listinfo/users