Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think it depends on the scale of the problem.</p> <p>You could write some generic JavaScript that shows and hides the form fields (then in the form itself you apply these css classes). This would work well for a relatively small number showing and hiding fields.</p> <p>If you want to go further than that you will need to think about developing dynamic forms in Django. I would suggest you don't modify the ['field'] in the class like Ghislain suggested. There is a good post here about <a href="http://www.b-list.org/weblog/2008/nov/09/dynamic-forms/" rel="nofollow noreferrer">dynamic forms</a> and it shows you a few approaches.</p> <p>I would imagine that a good solution might be combining the dynamic forms in the post above with the <a href="http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/" rel="nofollow noreferrer">django FormWizard</a>. The FormWizard will take you through various different Forms and then allow you to save the overall data at the end.</p> <p>It had a few gotchas though as you can't easily go back a step without loosing the data of the step your on. Also displaying all the forms will require a bit of a customization of the FormWizard. Some of the API isn't documented or considered public (so be wary of it changing in future versions of Django) but if you look at <a href="http://code.djangoproject.com/browser/django/trunk/django/contrib/formtools/wizard.py#L19" rel="nofollow noreferrer">the source</a> you can extend and override parts of the form wizard fairly easily to do what you need.</p> <p>Finally a simpler FormWizard approach would be to have say 5 static forms and then customize the form selection in the wizard and change what forms are next and only show the relevant forms. This again would work well but it depends how much the forms change on previous choices.</p> <p>Hope that helps, ask any questions if have any!</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to make a "workflow" form
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USOrange Box
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou can see ma solution in this post but I have a question : why do you suggest not to modify the self.fields['field_name'] ??
      singulars
      1. PO
      1. USGhislain Leveque
    2. COIt doesn't scale up well - if using type() to create forms dynamically is a much tidier and pythonic solution. Modifying self.fields is a bit of a hack and you end up making a mess of the __init__ and it requires changing the API for using the form. I'm actually writing a blog about this and will add the link here when I'm done as it explains in more. It comes down to personal choice in the end I suppose.
      singulars
      1. PO
      1. USOrange Box
 

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