StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1705076
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-11-10T01:14:22.160
FavoriteCount
0
LastActivityDate
2010-05-25T23:23:04.450
LastEditDate
2010-05-25T23:23:04.450
LastEditorUserId
153407
OwnerUserId
153407
ParentId
1704957
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
If you can set up the production server to access the SVN repo via a secure channel, such as https with webdav maybe try the following: Create a script on the Production server that allows you to enter a tag directory and/or revision number/date and perform an svn export. This way, the prod server is pulling the changes from svn. Now, if you have a way to have this script called securely from, say a commit script. Voila, you have automation. Most importantly, you do not want an automatic update performed to the prod server that you were not planning for. To solve this: The commit script should only call the prod update script when something is committed to "/path/to/tags/release/dir" Make sure only appropriate change control staff (or whoever currently controls the manual prod deplyment) have the ability to perform an svn copy to this directory in the repo. For example, say your repo is set up as: <pre><code>/yourWebsite --> /branches --> /trunk --> /tags ----> /releases </code></pre> The commit that would trigger the auto deployment to prod would be something like: <pre><code>svn copy https://mySvnRepo/yourWebSite/trunk \ https://mySvnRepo/yourWebSite/tags/releases/x.y \ -m "Tagging for production deployment" </code></pre> Rolling back can be achieved by making a commit to a previous releases directory. Note however, that this will not cause new files that were added to be rolled back. Of course, your mileage may vary; this is only a suggestion for your investigation. You should take time to consider the security implications and potential for disaster if set up incorrectly. Hope this helps, even if only to get you thinking of other solutions.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONeed advice on my PHP development solution
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDan McGrath
UserOwnerUserId
1. USDan McGrath
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONeed advice on my PHP development solution
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COThank you for your answer, that is an excellent idea.
 singulars
 PostPostId
 PO
 UserUserId
 USHubert Perron

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.