> Any links to an example ticket so I can keep a normal format for what
> im going to post? :)
take a look at the tickets with patches:
http://code.djangoproject.com/report/12
--
cheers,
Nikl
--~--~-~--~~~---~--~~
You received this message becau
hi,
while I really appreciate all of django's exciting new developments, I wonder
how some of workload could possibly be taken off the core developers'
shoulders by helping them wade through the currently 175 active tickets with
patches found on [1]. While it might be that someday I will encou
> I'd like to have a way to control through which foreign key
> fields it should expand, since I might not need all the data.
> That's also a point with the current implementation: It doesn't
> let me skip data fields not needed.
more and more I'm thinking this is definitely an excellent idea!! e.
hi Michael,
> It would be easier to comment on it if you would provide a patch
> with full path, so that track can recognize its context and
> display it properly. Look at the other patches if you don't see how.
after looking at other patches, I now called "svn diff" from the django
root-dir and
hi,
in case anybody else has been trying to include one2many-relations when
serializing the "one" side, take a look at
http://code.djangoproject.com/ticket/2843
would be great if someone else could test this as well. thanks!
--
cheers,
Nikl
--~--~-~--~~--
