Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Not trying to defend Django (that is not my job! :-)) just trying to give you some pointers on your list of limitations...</p> <blockquote> <p>as of december 2009 no model validation</p> </blockquote> <p>What exactly do you mean by this? Validation is available at the form level... And you can always override the <code>save()</code> method to implement whatever logic you desire and stop the save operation... Can you give an example of a scenario?</p> <blockquote> <p>the templating system is only good as far as you don't need custom template tags the idea to separate the design from the logic seemed good, it is frustrating, that I cannot sum 2 numbers in the view</p> </blockquote> <p><a href="http://docs.djangoproject.com/en/dev/ref/templates/builtins/#add" rel="noreferrer">Add two numbers?</a></p> <p>That said, you are not married to Django's templating system. You can use, for instance, <a href="http://lethain.com/entry/2008/jul/22/replacing-django-s-template-language-with-jinja2/" rel="noreferrer">Jinja2</a>.</p> <blockquote> <p>the template language is not designer friendly</p> </blockquote> <p>Uhhh... Why? Most designers I worked with had no problem working with template languages way more complex than Django's... Could you give an example of what you see as unfriendly? Maybe there is a work-around.</p> <blockquote> <p>the stack trace of an ex in a custom template tag is useless (if used with python 2.6). There is a patch for it, but it will go into django just in 1.2</p> </blockquote> <p>I haven't experienced this stack trace issue you discuss. You can always install the patch until Django 1.2 is around though. So it seems you have a solution available. </p> <blockquote> <p>django's orm (to connect to legacy systems) cannot handle blob fields</p> </blockquote> <p>If you are dealing with the need to store files in the database, maybe you should look at the <a href="http://code.welldev.org/django-storages/wiki/Home" rel="noreferrer">django-storages</a>' DatabaseStorage.</p> <blockquote> <p>cannot handle multi-column pk fields</p> </blockquote> <p>This, alongside with multiple database support, are the areas of real need of improvement - I agree. </p> <p>I suppose you could not use models (just straight SQL) for models that have the multi-column pk requirement (yes, it would kill the admin, but it is doable). Frankly - I don't have that problem in my models because I prefer surrogate primary keys - if a legacy model is on my way, I add a surrogate primary key to it - all the legacy code should continue to work and Django will be happy. But I do have complete control over the database tables, which might not be your case.</p> <p>Multi-column primary keys <a href="http://code.djangoproject.com/wiki/Version1.2Features" rel="noreferrer">are medium priority for the 1.2 release</a>.</p> <p>Multidb is <a href="http://code.djangoproject.com/wiki/Version1.2Features" rel="noreferrer">high priority for 1.2 release</a>.</p> <p>The 1.2 release is <a href="http://code.djangoproject.com/wiki/Version1.2Roadmap" rel="noreferrer">expected by March 2010</a>. Sure, the date is not written in stone. </p> <p>Given my experience with other frameworks, I would rather work around my issues and stick to Django.</p>
    singulars
    1. This table or related slice is empty.
    1. POTo what framework is it worth to switch from django
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScethegeek
    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
    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. COre: "Validation is available at the form level...", well, but as you might know, models aren't always constructed via forms. It would've been great if it was possible to actually perform validation in model's `save` method or fields' `to_python` methods. In fact, there is/was a "model validation" branch that did just that. I am not sure about its fate though (whether or not it is going to be merged into trunk for 1.2)
      singulars
      1. PO
      1. USshylent
    2. COI really don't see the advantage of having validation at the model level. I can't conjure a scenario where you would not benefit from using django forms. If it is user interaction that is creating the model, using the form makes complete sense (to me). If it is a programmatic interaction (i.e. no user interaction involved) that is creating the model, why would you need validation? As I said - it might be me being myopic on what are the scenarios. And if I ever needed to have some validation at the model - why not override the save method and do what I must?
      singulars
      1. PO
      1. UScethegeek
    3. COWell, of course you can just raise ValidationError anywhere, but surely there is little point in that, unless it is "blessed" by the framework's specification (like you are supposed to raise ValidationError in `clean`, `clean_*` and similar methods in forms, right?). My point is that validation is there to make sure, that unwanted data doesn't hit the database. As things are now, you can just initialize a model's instance with whatever values, call `save` and, _bam!_, there you have absolutely out of context data in your database.
      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