Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>"edit: PS - I thought about using the post_init signal... for the code that accesses the db, is that a good idea?"</p> <p>Never.</p> <p>If you have code that's accessing the model before the tables are created, you have big, big problems. You're probably doing something seriously wrong.</p> <p>Normally, you run syncdb approximately once. The database is created. And your web application uses the database.</p> <p>Sometimes, you made a design change, drop and recreate the database. And then your web application uses that database for a long time.</p> <p>You (generally) don't need code in an <code>__init__.py</code> module. You should (almost) never have executable code that does real work in an <code>__init__.py</code> module. It's very, very rare, and inappropriate for Django.</p> <p>I'm not sure why you're messing with <code>__init__.py</code> when <a href="http://code.google.com/p/django-cron/" rel="nofollow noreferrer">Django Cron</a> says that you make your scheduling arrangements in <code>urls.py</code>.</p> <hr> <p><strong>Edit</strong></p> <p>Clearing records is one thing.</p> <p>Messing around with <code>__init__.py</code> and Django-cron's <code>base.py</code> are clearly completely wrong ways to do this. If it's that complicated, you're doing it wrong.</p> <p>It's impossible to tell what you're trying to do, but it should be trivial.</p> <p>Your <code>urls.py</code> can only run after syncdb and after all of the ORM material has been configured and bound correctly.</p> <p>Your <code>urls.py</code> could, for example, delete some rows and then add some rows to a table. At this point, all syncdb issues are out of the way.</p> <p>Why don't you have your logic in <code>urls.py</code>?</p>
    singulars
    1. This table or related slice is empty.
    1. POKeep code from running during syncdb
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USS.Lott
    1. USS.Lott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POKeep code from running during syncdb
      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. COregarding the post_init signal, I realized that it didn't do what I thought it did, so that approach wouldn't work
      singulars
      1. PO
      1. USJiaaro
    2. COthe code snippet above got moved to the base.py file in django-cron, but as the design of the app stands, I think it is still necessary to clear all the records out of the database when the app gets started (since it doesn't remember jobs once you kill django or restart the server)
      singulars
      1. PO
      1. USJiaaro
 

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