StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14221129
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-08T17:54:13.977
FavoriteCount
0
LastActivityDate
2013-01-08T18:30:43.113
LastEditDate
2013-01-08T18:30:43.113
LastEditorUserId
1601059
OwnerUserId
1601059
ParentId
3567352
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I experienced this same error on Mac OS X 10.6 after I followed the instructions on the geodjango site and installed packages using Homebrew. Apparently, the Geodjango documentation gave some incorrect/outdated instructions about how to install it. To make Geodjango work, I followed several steps: <ol> <li>Right now, GeoDjango 1.4 does not play nice with PostGIS 2.0 (which is the version Homebrew installed when I followed the instructions in the GeoDjango documentation). So, I needed to install PostGIS 1.5. I did this using the following Terminal commands (for this to work, you must have Homebrew installed): <pre><code>brew tap homebrew/versions brew install postgis15 brew untap homebrew/versions </code></pre></li> <li>PostGIS 1.5 doesn't play nice with PostGreSQL 9.2 (which is the version Homebrew installed when I followed the Geodjango documentation's instructions). So, I installed PostGreSQL 9.1. I forget exactly what Homebrew commands I used to install PostGreSQL 9.1, but they should be similar to the previous step. </li> <li>In my case the prior steps weren't sufficient to get Geodjango operational. When I tried to run 'syncdb' in Django again, I discovered a new error in Terminal: <pre><code>django.core.exceptions.ImproperlyConfigured: Error loading psycopg module: No module named psycopg </code></pre></li> <li>I initially thought my copy of psycopg2 and PostgreSQL9.1 were not on my PYHTONPATH, so I added them. I also fiddled around to make sure django was running PostgreSQL 9.1 instead of 9.2. I used 'initdb /usr/local/var/postgres'. </li> <li>Then I needed to do some database configuration. I set up a template in PostGIS and set up a "role" (/user) for the database. To do this, I followed the instructions in the Geodjango documentation. I received numerous errors, but Googled them and found solutions pretty easily.</li> <li>Then GeoDjango started working properly! </li> </ol> This source was the most helpful one I found and links to other helpful urls that cover some of these issues in more detail: <a href="http://pragmaticstartup.wordpress.com/2012/09/26/installing-django-postgis-postgres-on-os-x-version-hell/" rel="nofollow">http://pragmaticstartup.wordpress.com/2012/09/26/installing-django-postgis-postgres-on-os-x-version-hell/</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POgeodjango syncdb errors. From geodjango tutorial
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBrian
UserOwnerUserId
1. USBrian
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
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.