StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4300224
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-11-29T01:29:59.333
FavoriteCount
0
LastActivityDate
2014-06-17T03:28:40.267
LastEditDate
2014-06-17T03:28:40.267
LastEditorUserId
232064
OwnerUserId
232064
ParentId
2721946
PostTypeId
2
Score
27
ViewCount
0
LastEditorDisplayName
text
Body
There are essentially two versions of the <code>getopt</code> command: the original version and the GNU enhanced version. The GNU enhanced version is backward compatible with the original version, so if you only use the features of the original version it will work with both. Detect which version of getopt is available You can detect which version is available and use the enhanced features if the GNU enhanced version is available, and limit yourself to the original features if the GNU enhanced version is not available. The enhanced version has a <code>-T</code> option for testing which version is available. <pre><code>getopt -T > /dev/null if [ $? -eq 4 ]; then # GNU enhanced getopt is available set -- `getopt --long help,output:,version --options ho:v -- "$@"` else # Original getopt is available set -- `getopt ho:v "$@"` fi </code></pre> Consider using built-in shell command <code>getopts</code> (with an "s") instead, because it is more portable. However, <code>getopts</code> does not support long options (e.g. <code>--help</code>). If you like long options, use <code>getopt</code> and use the above test to see if the GNU enhanced version of <code>getopt</code> is available or not. If the enhanced version is not available, the script can gracefully degrade to either using the original version of <code>getopt</code> (with no support for long option names and no whitespace support) or using <code>getopts</code> (with no support for long option names). Using GNU enhanced getopt properly Getting the GNU enhanced version to process arguments with whitespace properly is tricky. Here's how it is done: <pre><code>ARGS=`getopt --long help,output:,verbose --options ho:v -- "$@"` if [ $? -ne 0 ]; then echo "Usage error (use -h for help)" >&2 exit 2 fi eval set -- $ARGS # Parameters are now sorted: options appear first, followed by --, then arguments # e.g. entering: "foo bar" -o abc baz -v # produces: -o 'abc' -v -- 'foo bar' 'baz' </code></pre> The secret is to use <code>"$@"</code> where the double quotes are very important (in line 1), and to <code>eval</code> the set command (in line 6). So errors raised by <code>getopt</code> can be detected and handled, the call to <code>getopt</code> is done separately from the <code>eval</code> with the two linked by the ARGS variable. Complete working example <pre><code>PROG=`basename $0` getopt -T > /dev/null if [ $? -eq 4 ]; then # GNU enhanced getopt is available ARGS=`getopt --name "$PROG" --long help,output:,verbose --options ho:v -- "$@"` else # Original getopt is available (no long option names, no whitespace, no sorting) ARGS=`getopt ho:v "$@"` fi if [ $? -ne 0 ]; then echo "$PROG: usage error (use -h for help)" >&2 exit 2 fi eval set -- $ARGS while [ $# -gt 0 ]; do case "$1" in -h | --help) HELP=yes;; -o | --output) OUTFILE="$2"; shift;; -v | --verbose) VERBOSE=yes;; --) shift; break;; # end of options esac shift done if [ $# -gt 0 ]; then # Remaining parameters can be processed for ARG in "$@"; do echo "$PROG: argument: $ARG" done fi echo "$PROG: verbose: $VERBOSE" echo "$PROG: output: $OUTFILE" echo "$PROG: help: $HELP" </code></pre> This example can be downloaded from <a href="https://gist.github.com/hoylen/6607180" rel="noreferrer">https://gist.github.com/hoylen/6607180</a> The comparison table on <a href="http://en.wikipedia.org/wiki/Getopts" rel="noreferrer">Wikipedia's entry on getopts</a> compares the different features.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCross-platform getopt for a shell script
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USHoylen
UserOwnerUserId
1. USHoylen
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
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
 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.