Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Best implimentation I have seen based on Google IO Pro Tips 2010 is the RoboSpice library, which is REST based and very cleverly works with the Activity lifecycle as to not leak memory.</p> <p>Quick <a href="https://raw.github.com/octo-online/robospice/master/gfx/RoboSpice-InfoGraphics.png" rel="noreferrer">infographic</a> the library is <a href="https://github.com/octo-online/robospice" rel="noreferrer">here</a></p> <ul> <li>Loaders are designed for database, not REST, they are reset on activity reset meaning you loose your data.</li> <li>Async task, just no.</li> <li>Intent Service + Result receiver is basically how RoboSpice work, so if you are building your own lib, I would take this approach!</li> <li>Service is also good, similar to the IntentService Method, but IntentService works a little better in this instance.</li> </ul> <p>The <code>Service</code> method maybe better, <a href="https://github.com/octo-online/robospice/blob/release/robospice-core-parent/robospice/src/main/java/com/octo/android/robospice/SpiceService.java" rel="noreferrer">look at the robospice service</a> they use an <code>ExecutorService</code> which terminates the <code>Service</code> when it has run out of <code>Requests</code> to work through, this is more Java concurrency than Android specific. Main thing to note that the service runs whilst processing requests then terminates its self if their are none left.</p> <p>The advantage of using the <code>ExecutorService</code> or any type of thread pool, is that you can define how many requests you can run at once. unless you have a very fast connection 2-4 is the most i would ever suggest.</p>
    singulars
    1. This table or related slice is empty.
    1. POREST API Client Library for Android
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris.Jenkins
    1. USChris.Jenkins
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POREST API Client Library for 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. COThanks :) That really makes the decision easier. But now i have one more question, considering we would use IntentService, Since IntenetSerive processes only one request at a time and new requests are queued how do we go about making simultaneous REST API calls ? Say, if the list of users is being retrieved (which takes ~10secs) and user tries to send a message in between of that operation ?
      singulars
      1. PO
      1. USMadhur
    2. COEither your own version of IntentService or Accept to run one request at a time, Google has changed a lot of threading in the Android SDK to do one at a time now. Unless you need it now, the accepted convention is just process a queue of 'tasks'. Saying that, I think RoboSpice does a few requests at once, have a look at their source.
      singulars
      1. PO
      1. USChris.Jenkins
    3. COOne ugly approach i can think of is implementing multiple IntentService which basically do the same operation of calling a REST API. That way, we can make simultaneous requests, but it would add a lot of code redundancy. Your thoughts on it ?
      singulars
      1. PO
      1. USMadhur
 

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