title: Why is the paradigm of "direct database connection" not welcomed by the Android platform?
body: <p>When I say "direct database connection", I meant to use a JDBC-alike driver to call and run a remote database query within the context of an activity, just like using an SQLite database to store the local parameters.</p>
  
  <p>Until I realized that I could barely find any tutorials or documents on the Internet regarding this way of database connection, I thought, regardless of the unstable Wi-Fi/3G network bore by most if not all Android devices, to connect to a database should be done like so.</p>
  
  <p>Even in Android SDK, only local database access (a.k.a <code>android.database.sqlite</code>) is supported intrinsically. And it's stated in the description of <a href="http://developer.android.com/reference/java/sql/package-descr.html" rel="nofollow noreferrer">java.sql</a> API that <strong>you must provide your own JDBC driver</strong> in order to use this API.</p>
  
  <p>Then I started to realize if my intention of directly connecting a database is incorrectly in the first place in the realm of Android.</p>
  
  <p>I have read many books, wikis, and forums, including numerous answers provided on Stack&nbsp;Overflow. It appears to me that many people are concentrating on getting something done, and discussions used to start with "How can I design a RESTful web service for my Android device?". However, I need a thorough understanding! And I also need authoritative citations from the original Android developers.</p>