Hi,
The form_class property for generic views such a
django.views.generic.create_update.* should accept either a ModelForm?
class or a ModelForm? object. This would allow generic "wrapper views"
to easily inject run-time data into the form instance.
Here is an example:
def project_new(request):
So the answer to the question "Can I get the right instances with one
single and only DB query" seems to be:
"No, you cannot do so without touching the Django orm code".
Am I right?
On Aug 24, 1:52 am, Russell Keith-Magee
wrote:
>
> > Or if this is planned for some future release.
>
> As I said
On Sun, Aug 23, 2009 at 11:00 PM, Andrea Zilio wrote:
>
> Great, but that wasn't exactly what I was looking for.
>
> What I need is a way to get the right instances from a *single* query.
>
> This means that I should do LEFT JOINS on direct subclasses of the
> base class.
>
> What I need to know i
Yeah, named urls didn't direct fix the problem. I've submitted a new
patch.
Now someone just needs to write the tests :P
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
Hi all,
I've been working with Django for a bit now, and decided to try
contributing, by submitting a patch to fix a problem I ran into at
work. This seems like something that requires a design decision.
So, what do you think?
--Jukka
--~--~-~--~~~---~--~~
You r
So over the weekend I've been thinking about the problem of the two
potential use cases for following relationship fields in Django
models: 1) All (or most) models exist on every db instance and the
data is sharded somehow or 2) Different models exist on different db
instances but all data for a p
Great, but that wasn't exactly what I was looking for.
What I need is a way to get the right instances from a *single* query.
This means that I should do LEFT JOINS on direct subclasses of the
base class.
What I need to know is if this is somehow possible without editing the
Django core, but us
On Sun, Aug 23, 2009 at 1:54 PM, Andrea Zilio wrote:
>
> So seems that this idea was in fact rejected because of the O(# of
> nodes in the inheritance tree) joins
> needed to get all the fields from subclass tables.
>
You may want to loook at Alex's post on the subject:
http://lazypython.blogspo
Thanks! I think I've found the discussion you're talking about:
http://groups.google.com/group/django-developers/browse_thread/thread/7d40ad373ebfa912/a20fabc661b7035d
So seems that this idea was in fact rejected because of the O(# of
nodes in the inheritance tree) joins
needed to get all the fie
On Sun, Aug 23, 2009 at 9:18 AM, Andrea Zilio wrote:
>
> Hi all,
>
> Here's what I'm talking about:
> You have 3 models: Place, Restaurant and Cinema where Restaurant and
> Cinema both inherits from Place.
> So in the database you have some simple places, some places which
> really are Cinemas and
10 matches
Mail list logo
