StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If I got it correctly, you can just use the <code>--settings</code> switch to point manage.py to the <code>dj_tornado.py</code>, which is your settings file after all</p> <h2>Update 1</h2> <p>from the help, available at <code>python manage.py help</code>: </p> <pre> Options: --settings=SETTINGS The Python path to a settings module, e.g. "myproject.settings.main". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used. </pre> <p>So I would try this:</p> <pre>python manage.py syncdb --settings=dj_tornado</pre> <h2>Update 2</h2> <p>Another error, another update to the answer!<br> First of all, consider that that blog post is quite old (september 2009). Django's <pre>DATABASES</pre> setting <a href="http://docs.djangoproject.com/en/1.2/ref/settings/#databases" rel="nofollow">has been updated since 1.2</a>.</p> <p>The syntax in the blog post was:</p> <pre><code>settings.configure(DATABASE_ENGINE='sqlite3', DATABASE_NAME='dev.db') </code></pre> <p>With Django 1.2.X this is surely not correct. This would be the equivalent version:</p> <pre><code>settings.configure(DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': 'dev.db' } }) </code></pre> <p>(sorry for the horrible formatting of the code).</p> <p>If this <em>still</em> won't work, I'd consider creating a “standard” Django settings file to import. But my bet is on the db settings syntax.</p> <h2>Last update, I swear</h2> <p>Have you tried using django-admin.py again with the new syntax? If so, and still didn't work, a minimal settings.py would be just this:</p> <pre><code>DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': 'dev.db' } } </code></pre> <p>You can also keep the original configuration inside dj_tornado.py and use settings.py just to do syncdb.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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