Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would absolutely learn Java first. Don't bother learning things like servlets, Swing etc - but learn:</p> <ul> <li>The core language</li> <li>Collections</li> <li>IO</li> <li>String handling</li> </ul> <p>Trying to learn these while <em>also</em> learning a completely new environment will make it a lot harder to work out where you're going wrong.</p> <p>Note that this isn't specific to Android - I'd always encourage developers to learn the "core" of a new platform before learning "peripheral" technologies such as native UIs or web frameworks.</p> <p>I've seen people try to do this before - literally asking complicated questions about advanced scenarios, while not understanding the basics of the language. Sometimes the problem they've been having has been due to the complex API they were using, and sometimes it's been due to the basic misunderstandings - <em>but the problems looks exactly the same to them</em>. They can't tell the difference between not understanding how method arguments are passed, and having difficulty with cross-threading UI operations. As far as they're concerned, "something has gone wrong." Every step is painful when you don't have a solid foundation.</p> <p>Aside from anything, as boring as console applications with no interaction might be, they're <em>really</em> great for just testing something quickly. You typically don't need to worry about threading, permissions, graphics, resources etc. Another good way to test your understand is via unit tests. Rather than a normal test-first approach, write a method and predict its output with unit tests, until you run out of interesting situations to test. Once you're done, you've got a complete record of what the code does - keep it for later on, in case you need to revisit the concept you were testing.</p>
    singulars
    1. This table or related slice is empty.
    1. POShould I learn Java before learning Android
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJon Skeet
    1. USJon Skeet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POShould I learn Java before learning Android
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAgreed - I am a developer who has already done a lot of programming in C# and Java. It wasn't hard to get in and make code behind work for the first Android app I'm doing. So most of my learning is now going to be UI interaction and phone specific stuff. But without the Java knowledge, I'd be lost.
      singulars
      1. PO
      1. UStheJerm
    2. CO@JonSkeet and what if I am an expert C# developer, can I dive into android development?
      singulars
      1. PO
      1. USAli Issa
    3. CO@AliIssa: I would still take a little time to experiment with desktop Java first, just to find your feet. Spend a week exploring the language and core APIs that way, *then* start Android.
      singulars
      1. PO
      1. USJon Skeet
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload