StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19189930
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-04T20:09:55.663
FavoriteCount
0
LastActivityDate
2017-01-21T13:51:36.033
LastEditDate
2017-01-21T13:51:36.033
LastEditorUserId
2595183
OwnerUserId
189134
ParentId
19189813
PostTypeId
2
Score
231
ViewCount
0
LastEditorDisplayName
text
Body
<a href="https://docs.djangoproject.com/en/dev/ref/databases/#mysql-notes" rel="noreferrer">MySQL support</a> is simple to add. In your <code>DATABASES</code> dictionary, you will have an entry like this: <pre><code>DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'DB_NAME', 'USER': 'DB_USER', 'PASSWORD': 'DB_PASSWORD', 'HOST': 'localhost', # Or an IP Address that your DB is hosted on 'PORT': '3306', } } </code></pre> You also have the option of utilizing MySQL <a href="https://docs.djangoproject.com/en/1.7/ref/databases/#connecting-to-the-database" rel="noreferrer">option files</a>, as of Django 1.7. You can accomplish this by setting your <code>DATABASES</code> array like so: <pre><code>DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'OPTIONS': { 'read_default_file': '/path/to/my.cnf', }, } } </code></pre> You also need to create the <code>/path/to/my.cnf</code> file with similar settings from above <pre><code>[client] database = DB_NAME host = localhost user = DB_USER password = DB_PASSWORD default-character-set = utf8 </code></pre> With this new method of connecting in Django 1.7, it is important to know the order connections are established: <pre class="lang-none prettyprint-override"><code>1. OPTIONS. 2. NAME, USER, PASSWORD, HOST, PORT 3. MySQL option files. </code></pre> <blockquote> In other words, if you set the name of the database in OPTIONS, this will take precedence over NAME, which would override anything in a MySQL option file. </blockquote> <hr> If you are just testing your application on your local machine, you can use <pre><code>python manage.py runserver </code></pre> Adding the <code>ip:port</code> argument allows machines other than your own to access your development application. Once you are ready to deploy your application, I recommend taking a look at the chapter on <a href="http://www.djangobook.com/en/2.0/chapter12.html" rel="noreferrer">Deploying Django</a> on the <a href="http://www.djangobook.com/en/2.0/index.html" rel="noreferrer">djangobook</a> Mysql default character set is often not utf-8, therefore make sure to create your database using this sql: <pre><code>CREATE DATABASE mydatabase CHARACTER SET utf8 COLLATE utf8_bin </code></pre> If you are using <a href="http://dev.mysql.com/doc/connector-python/en/connector-python-django-backend.html" rel="noreferrer">Oracle's MySQL connector</a> your <code>ENGINE</code> line should look like this: <pre><code>'ENGINE': 'mysql.connector.django', </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSetting Django up to use MySQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USFeedTheWeb
UserOwnerUserId
1. USAndy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSetting Django up to use MySQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.