Databases
StackOverflow2013
Postsdbo
POPassing kwargs from template to view?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPassing kwargs from template to view?
    primarykey
    data
    text
    <p>As you may be able to tell from my questions, I'm new to both python and django. I would like to allow dynamic filter specifications of query sets from my templates using <code>**kwargs</code>. I'm thinking like a select box of a bunch of kwargs. For example:</p> <pre><code> &lt;select id="filter"&gt; &lt;option value="physician__isnull=True"&gt;Unassigned patients&lt;/option&gt; &lt;/select&gt; </code></pre> <p>Does django provide an elegant solution to this problem that I haven't come across yet?</p> <p>I'm trying to solve this in a generic manner since I need to pass this filter to other views. For example, I need to pass a filter to a paginated patient list view, so the pagination knows what items it's working with. Another example is this filter would have to be passed to a patient detail page so you can iterate through the filtered list of patients with prev/next links.</p> <p>Thanks a bunch, Pete</p> <p><strong>Update:</strong></p> <p>What I came up with was building a <code>FilterSpecification</code> class:</p> <pre><code>class FilterSpec(object): def __init__(self, name, *args): super(FilterSpec, self).__init__() self.name = name self.filters = [] for filter in args: self.add(filter) def pickle(self): return encrypt(pickle.dumps(self)) def add(self, f): self.filters.append(f) def kwargs(self): kwargs = {} for f in self.filters: kwargs = f.kwarg(**kwargs) return kwargs def __unicode__(self): return self.name class Filter(object): def __init__(self, key, value): super(Filter, self).__init__() self.filter_key = key self.filter_value = value def kwarg(self, **kwargs): if self.filter_key != None: kwargs[self.filter_key] = self.filter_value return kwargs </code></pre> <p>I then can filter any type of model like this:</p> <pre><code>filterSpec = FilterSpec('Assigned', Filter('service__isnull', False))) patients = Patient.objects.filter(**filterSpec.kwargs()) </code></pre> <p>I pass these filterSpec objects from the client to server by serializing, compressing, applying some symmetric encryption, and url-safe base-64 encoding. The only downside is that you end up with URLs looking like this:</p> <pre><code>http://127.0.0.1:8000/hospitalists/assign_test/?filter=eJwBHQHi_iDiTrccFpHA4It7zvtNIW5nUdRAxdiT-cZStYhy0PHezZH2Q7zmJB-NGAdYY4Q60Tr_gT_Jjy_bXfB6iR8inrNOVkXKVvLz3SCVrCktGc4thePSNAKoBtJHkcuoaf9YJA5q9f_1i6uh45-6k7ZyXntRu5CVEsm0n1u5T1vdMwMnaNA8QzYk4ecsxJRSy6SMbUHIGhDiwHHj1UnQaOWtCSJEt2zVxaurMuCRFT2bOKlj5nHfXCBTUCh4u3aqZZjmSd2CGMXZ8Pn3QGBppWhZQZFztP_1qKJaqSVeTNnDWpehbMvqabpivtnFTxwszJQw9BMcCBNTpvJf3jUGarw_dJ89VX12LuxALsketkPbYhXzXNxTK1PiZBYqGfBbioaYkjo%3D </code></pre> <p>I would love to get some comments on this approach and hear other solutions.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USslypete
    1. USslypete
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPassing kwargs from template to view?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COLooks like a good way to open up a security hole where people can run custom queries on your DB.
      singulars
      1. POPassing kwargs from template to view?
      1. USFogleBird
    2. COIf you maintain a list of allowed keys, such as physician* or first_name*, I don't see how this will cause a problem.
      singulars
      1. POPassing kwargs from template to view?
      1. USslypete
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload