StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPostgreSQL development workflow
primarykey
Id
17960955
data
AcceptedAnswerId
18159013
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-31T03:15:10.243
FavoriteCount
0
LastActivityDate
2013-08-10T05:42:09.663
LastEditDate
LastEditorUserId
0
OwnerUserId
2009500
ParentId
0
PostTypeId
1
Score
4
ViewCount
1047
LastEditorDisplayName
text
Body
I am starting to build a new database for my project using PostgreSQL. (I am new to PostgreSQL and database by the way.) I think my development workflow is very bad, and here is a part of it: <ol> <li>create table/view/function with pgAdmin.</li> <li>determine the name of the file before saving the code. The goal is to be able to recreate the database automatically by running all the saved scripts, I need to know the order to run these scripts for dependency reason. So I add a number for each file indicating the order. for example: 001_create_role_user.ddl, 002_create_database_project.ddl, 013_user_table.ddl</li> <li>save the code.</li> <li>commit the file to repository using GIT.</li> </ol> Here are some bads I can think of: <ul> <li>I can easily forget what changes I made. For example, created a new type, or edited comment</li> <li>It is hard to determine a name (order) for the file.</li> <li>Change the code would be a pain in the ass, especially when the new code changes the order.</li> </ul> So my workflow is bad. I was wondering what other Postgres developers' workflow looks like. Are there any good tools (free or cheap) for editing and saving scripts? good IDE maybe? It would be great if I can create automated unit tests for the database. Any tool for recreating the database? CI server tool? Basically I am looking for any advice, good practice, or good tool for database development. (Sorry, this question may not fit for the Q&A format, but I do not know where else to ask this question.) 
Tags
<database><postgresql><workflow><development-environment>
Title
PostgreSQL development workflow
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USXin
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POPostgreSQL development workflow
 UserUserId
 USXin
 VoteTypeVoteTypeId
 VTBountyStart
2. VO
 singulars
 PostPostId
 POPostgreSQL development workflow
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POPostgreSQL development workflow
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
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.