Skip to main content

Accessing Android SQLite Database


When developing Android Application that stores data in SQLite Database, it is very useful to directly access the Database on the Emulator or Real Device from the Terminal to Debug or Test.
For instance as a Developer I want to verify data is saved in Database, debugging SQL Queries etc.

Here are the steps to be followed to connect to the SQLDatabase of the Device From the Command prompt

First Start the Android Emulator or connect a Android Device with the System.  Once The Device is connected we can access the Shell of the device though ADB. Note that ADB should be installed on the System from where we want to access the Android Database(s).

After the Device is connected open a Terminal and follow the following steps.

1) Get The List of Active Devices

$adb devices 
List of devices attached emulator-5554 device

This will give list of emulator or Devices connected to the System. (For me it is showing only one active Emulator emulator-5554)

Say we want to connect to database of the Device  emulator-5554. Get shell access to one of the Device(emulator-5554)

2) Access Shell of the target emulator
$ adb -s emulator-5554 shell
This will lunch the  shell for the target Device.

Now to access the Database we have to go to the following location

3) Go to Data Folder on the Device
Go to the data location on the Device /data/data/com.sidd.learnit/databases.
Here com.sidd.learnit is the name of the package. Under this folder the database is created in Android. One in this folder, I see the following under it.

These are the two databases for the Application that I deployed on the emulator-5554.

Here it is showing two databases
learnt and testappdb.

4) Open the SQLite Database learnt
sqlite3 learnit

It will lunch the sqlite3 command prompt.

Now we can execute commands to play around with the data.

See all the Tables in the Database .tables

Get all the data from Table hq_users Select * from hq_users

Comments

Popular posts from this blog

Masking Credit Card number in Java

Sometimes we need to mask crucial information like Credit Card Numbers, CVV numbers etc before storing  or logging the information. This example mask Credit Card Number (Except last 4 Digit) from a Text which contains information along with Credit Card Number.

The following example demonstrates how we can easily mask the credit card with Matcher and Pattern Classes. This Sample Code uses Matcher and Pattern.
Pattern Used in this sample is not optimized for Credit Card Numbers, this pattern will get any numerical numbers in the String Content.  Based on the Credit Card Type a more efficient and Strict RegEx can be used to mask the Credit Card.
/**Mask the Credit card number but last four digit value **/   Pattern PATTERN = Pattern.compile("[0-9]+"); String message = content; Matcher matcher = PATTERN.matcher(message); String maskingChar = "*"; StringBuilder finalMask = new StringBuilder(maskingChar); while …

Converting Java Map to String

Java Collections framework, String manipulation etc is something that we often encounter in Development process.
For processing collections (like checking null/empty, Intersection, Disjunction) We do have some of the very use full libraries.

Some of the Collection related libraries are Apche Commons Collections and Google  Collections(Guava).

Problem Use Case

This article explains how to convert a Java Map to String(and vice versa) using different libraries and technique.

One way is to use StringBuilder(Or String) and loop though the Map and build the String by applying some sort of separator ( for key:value and entry). Here we have to take care of the null value etc.

Without Any Library
If we want to convert the map to a String with key value separator and also individual entry seperator in the resulting String, we have to write code for that. For a simple Map, we have to iterate though the map, take care of the null values etc. Following is a sample to get String built out from Map C…

Invoking EJB deployed on a remote machine

Invoking EJB deployed on a remote machineIn case we are calling remote ejb( ejb deployed on remote machines),The JNDI lookup might lookup like,Properties env = new Properties();env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");env.put(Context.PROVIDER_URL, "XX.XXX.XX.XX:1099");env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); Context ctx = new InitialContext(env);If we are calling local ejb then we can simply create InitialContext without any parameters.Like,Context ctx = new InitialContext();