Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When I used <code>extra</code> on formsets in similar situation I ended up having to include all the required fields from the model in the form, as HiddenInputs. A bit ugly but it worked, curious if anyone has a hack-around.</p> <p><strong>edit</strong><br> I was confused when I wrote above, I'd just been working on formsets using <code>extra</code> with <code>initial</code> to pre-fill the extra forms and also I hadn't fully got all the details of your questions.</p> <p>If I understand correctly, where you instantiate the <code>LineFormSet</code>s in <code>add_fields</code> each of those will point to the same <code>Result</code> instance?</p> <p>In this case you don't really want to supply <code>result</code> in <code>initial</code> due to the problems you're having. Instead you could remove that field from the LineForm model-form altogether and customise the <code>LineFormSet</code> class something like:</p> <pre><code>class LineFormSet(forms.BaseModelFormSet): # whatever other code you have in it already # ... # ... def __init__(self, result, *args, **kwargs): super(LineFormSet, self).__init__(*args, **kwargs) self.result = result def save_new(self, form, commit=True): instance = form.save(commit=False) instance.result = self.result if commit: instance.save() return instance def save_existing(self, form, instance, commit=True): return self.save_new(form, commit) </code></pre> <p>(this should be ok in Django 1.3 and 1.4, not sure other versions)</p> <p>so the relevant part of your <code>add_fields</code> method would look like:</p> <pre><code> form.nested = [ LineFormSet( result = instance, queryset = q, #data=self.data, instance = instance, prefix = 'LINES_%s' % pk_value)] prefix = 'lines-%s' % pk_value, )] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCorrect way to save nested formsets in Django
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAnentropic
    1. USAnentropic
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCorrect way to save nested formsets in Django
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COCan you explain a little more about how that works? I'm already including one required field as a HiddenInput, which is the source of my problems (this being my first Django project doesn't help either)
      singulars
      1. PO
      1. USJohnWoltman
    2. COI didn't read your question carefully enough, it just reminded me of something I'd been doing in my own code. I've revised my answer with something hopefully more helpful.
      singulars
      1. PO
      1. USAnentropic
    3. COThat makes sense from a Django-perspective, but by removing the ``result`` field from the model code would mean that Django would no longer save the result into the correct table anymore. I think. Being new to Django I'm not quite sure.
      singulars
      1. PO
      1. USJohnWoltman
 

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