StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12558781
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-24T04:17:26.343
FavoriteCount
0
LastActivityDate
2012-09-24T04:17:26.343
LastEditDate
LastEditorUserId
0
OwnerUserId
1141466
ParentId
12558547
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
By default, the Android system redirects <code>stdout</code> (<code>System.out</code>) output to <code>/dev/null</code>, which means your messages are lost. Instead, the common pattern to log debug strings in Android is the following <pre><code>import android.util.Log; </code></pre> Then at the top of your class <code>YourClass</code> <pre><code>private static final String TAG = YourClass.class.getSimpleName(); </code></pre> And to log debug strings you need to call <pre><code>Log.d(TAG, "your debug text here"); </code></pre> which in your case results in <pre><code>package com.test1.nus; import android.util.Log; import android.os.Bundle; import android.app.Activity; import android.view.Menu; public class MainActivity extends Activity { private static final String TAG = MainActivity.class.getSimpleName(); @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); Log.d(TAG, "Hello"); .... } </code></pre> Finally you can see your debug strings in Eclipse via <code>Windows > Show view > Other</code> and select <code>LogCat</code> and if required filter by the tag of <code>YourClass</code>. However, if you really need to see messages written by <code>System.out.println</code> you need to tell Android to route them to logcat via the following shell commands <pre><code>$ adb shell stop $ adb shell setprop log.redirect-stdio true $ adb shell start </code></pre> and then you will be able to see your debug messages in Eclipse via LogCat view and the tag <code>stdout</code>. You can get more details from the official documentation here <a href="http://developer.android.com/tools/debugging/debugging-log.html" rel="nofollow">http://developer.android.com/tools/debugging/debugging-log.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POoutput for System.out.print("Hello") in Android program
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USovmjm
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.