StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17961470
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-31T04:12:46.510
FavoriteCount
0
LastActivityDate
2013-07-31T04:12:46.510
LastEditDate
LastEditorUserId
0
OwnerUserId
215651
ParentId
17960955
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You're not far off. I'm a Java developer, not a DBA, but building out the database as a project grows is an important task for the teams I've been on, and here's how I've seen it done best: <ol> <li>All DB changes are driven by DDL (SQL create, alter, or delete statements) plain text scripts. No changes through the DB client. Use a text editor that supports syntax highlighting like vim or notepad++, as the highlighting can help you find errors before you run the script.</li> <li>Use a number at the beginning of each DDL script to define the order that scripts are run in. Base scripts have lower numbers. As the project grows, use alter new alter scripts to change the table, don't redefine the table in the initial script.</li> <li>Use a script and the psql client to load the DDL scripts from lowest to highest. Here's the bash script we use. You can use it as a base for a .bat script on windows.</li> </ol> <blockquote> #!/bin/bash export PGDATABASE=your_db export export PGUSER=your_user export export PGPASSWORD=your_password for SQL_SCRIPT in $( find ./ -name "*.sql" -print | sort); do <pre><code>echo "**** $SQL_SCRIPT ****" psql -q < $SQL_SCRIPT </code></pre> done </blockquote> <ol> <li>As the project grows, use new alter scripts to change the table, don't redefine the table in the initial script.</li> <li>All scripts are checked into source control. Each release is tagged so you can regenerate that version of the database in the future.</li> <li>For unit testing and CI, most CI servers can run a script to drop and recreate a schema. One oft-cited framework for PostGresql unit testing is <a href="http://pgtap.org/" rel="nofollow">pgTAP</a></li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPostgreSQL development workflow
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USlreeder
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.