On 1/17/06, scum <[EMAIL PROTECTED]> wrote:
> Method 1 works with keywords that want lists. For example.. the order
> by clause works in method 1 but not in method 2. (?order_by=city)
>
> Method 2 works with keywords that do not require a list. For example,
> the limit and offset keywords work i
I'm having partial success with the code given here. Let me clarify
the two methods I am using.
Method 1:
leads.get_list(**request.GET)
Method 2:
params = dict(request.GET.items())
milestones.get_values(**params)
Method 1 works with keywords that want lists. For example.. the order
by clause
since my server is down again, i can´t verify the code.
anyway, thanks everybody for your help.
patrick
Am 17.01.2006 um 16:19 schrieb Adrian Holovaty:
On 1/17/06, scum <[EMAIL PROTECTED]> wrote:
Okay- that is a lot trickier. Here's some yucky code that uses the
exec
command to accomplish
hmm, i thought this is quite easy as it´s already used in the
admin-interface (with filters).
thanks for the code,
patrick
Am 17.01.2006 um 16:14 schrieb scum:
Okay- that is a lot trickier. Here's some yucky code that uses the exec
command to accomplish the same goal... but it's definitel
On 1/17/06, scum <[EMAIL PROTECTED]> wrote:
> Okay- that is a lot trickier. Here's some yucky code that uses the exec
> command to accomplish the same goal... but it's definitely not the
> elegant solution you are looking for...
>
> q = []
> for key, value in request.GET.items():
>
On 1/17/06, patrick kranzlmüller <[EMAIL PROTECTED]> wrote:
> unfortunately, it doesn´t.
You're right. You have to consider that request.GET and request.POST
are MultiValueDicts. If you don't expect one key to have more than one
value, something like this might work:
milestones_list = milesto
What error are you getting when you try
"milestones.get_list(**request.GET)"?
Okay- that is a lot trickier. Here's some yucky code that uses the exec
command to accomplish the same goal... but it's definitely not the
elegant solution you are looking for...
q = []
for key, value in request.GET.items():
q.append ( "%s = %s" % (key, value) )
unfortunately, it doesn´t.
Am 17.01.2006 um 15:53 schrieb Andreas Stuhlmüller:
On 1/17/06, patrick kranzlmüller <[EMAIL PROTECTED]> wrote:
actually, i don´t really know my query parameters.
could be responsible__id__exact=5
or status__exact=1
or responsible__id__exact=5&status__exact=5
... a
On 1/17/06, patrick kranzlmüller <[EMAIL PROTECTED]> wrote:
> actually, i don´t really know my query parameters.
> could be responsible__id__exact=5
> or status__exact=1
> or responsible__id__exact=5&status__exact=5
> ... and so on.
>
> so, it´d be nice to have something like milestones_list =
> m
thanks for answering.
actually, i don´t really know my query parameters.
could be responsible__id__exact=5
or status__exact=1
or responsible__id__exact=5&status__exact=5
... and so on.
so, it´d be nice to have something like milestones_list =
milestones.get_list(x), where x is the query.
th
All get variables are automagically placed into the request.GET
dictionary. In your example:
http://mysite.com/manage/projects/1/milestones/?responsible__id__exact=1
Your variable `responsible__id__exact` would be obtained through the
code:
myVar = request.GET["responsible__id__exact"]
or
myVar =
my url looks like:
http://mysite.com/manage/projects/1/milestones/?responsible__id__exact=1
in the user-group, i found a posting where adrian said:
"The query parameters are, essentially, the same as keyword arguments
that can be passed to get_list(). "
can anybody give me a hint on how to ac
13 matches
Mail list logo
