Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Django has a <a href="https://docs.djangoproject.com/en/dev/ref/models/instances/#validating-objects" rel="noreferrer">model validation</a> system in place since version 1.2.</p> <p>In comments sebpiq says "Ok, now there is a place to put model validation ... except that it is run only when using a ModelForm! So the question remains, when it is necessary to ensure that validation is respected at the db-level, what should you do? Where to call full_clean?"</p> <p>It's not possible via Python-level validation to ensure that validation is respected on the db level. The closest is probably to call <code>full_clean</code> in an overridden <code>save</code> method. This isn't done by default, because it means everybody who calls that save method had now better be prepared to catch and handle <code>ValidationError</code>. </p> <p>But even if you do this, someone can still update model instances in bulk using <code>queryset.update()</code>, which will bypass this validation. There is no way Django could implement a reasonably-efficient <code>queryset.update()</code> that could still perform Python-level validation on every updated object.</p> <p>The only way to really guarantee db-level integrity is through db-level constraints; any validation you do through the ORM requires the writer of app code to be aware of when validation is enforced (and handle validation failures).</p> <p>This is why model validation is by default only enforced in <code>ModelForm</code> - because in a ModelForm there is already an obvious way to handle a <code>ValidationError</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. PODjango model fields validation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCarl Meyer
    1. USCarl Meyer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODjango model fields validation
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGreat, great, this is just great! I've skimmed through the source (by the way, is there any way to access the documentation as it can be done with trunk?) and it seems like just the thing I need. I mean, I am all for rolling my own, but django is _excellent_ at providing a uniform way of doing things (well, IMO, anyway).
      singulars
      1. PO
      1. USshylent
    2. COCheckout that branch, make sure you have docutils and Sphinx installed, then go into the docs/ directory and run "make html". That should build the docs in HTML form just like they are on the Django website, and you can access them locally.
      singulars
      1. PO
      1. USCarl Meyer
    3. COOk, I am back from reading the source (in particular `models/fields/__init__.py`, models/base.py and core/validators.py), since the documentation as of now says nothing about model validation. One should note, however, that it works almost the same as forms validation (at least, the general logic is more or less the same). Anyway, this is something I was looking for. I just hope my apps won't break horribly if I just switch from the trunk to this branch.
      singulars
      1. PO
      1. USshylent
 

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