Refactors the DBUtils and DatabaseUtils class to make it cleaner, simpler and easier to use:

• Move DBUtils and DatabaseUtils methods into DatabaseAnalyzer and StatementGenerator
• Moves the SQL queries from DatabaseAnalyzer into classes that implement the Query interface
• Moves query execution from DatabaseAnalyzer to QueryExecutor
• Refactors code in DatabaseAnalyzer: consolidating duplicate code, simplifying methods, adding Column object to replace Map<String, String>
• Deprecate public methods in DBUtils and DatabaseUtils

I've added a gradle script that sets some properties that are necessary to publish to bintray and then it uses external scripts that make all the magic.

This is the first one: https://gist.github.com/hal9002/0772dffbd8a6a81bc176

This first script uses this other script https://gist.github.com/hal9002/691bbf3340dde3a4591d to generate all the files needed to publish to a maven repo (thanks to @blundell ) and it also sets some basic configuration for bintray and applies the bintray gradle plugin.

The first gist can be modified to allow more customisation if necessary

:x: do not merge yet, I need to create an API key for the novoda account in bintray

But can be reviewed.

I noticed that multiple notifications are sent when bulkInsert is used. I figured out this because you iterating each ContentValue and run an individual transaction insert on the item.

@Override
public int bulkInsert(Uri uri, ContentValues[] values) {
    int numValues = values.length;
    SQLiteDatabase mDb = mOpenHelper.getWritableDatabase();
    mDb.beginTransactionWithListener(this);
    try {
        for (int i = 0; i < numValues; i++) {
            Uri result = insertInTransaction(uri, values[i]);
            if (result != null) {
                mNotifyChange = true;
            }
            mDb.yieldIfContendedSafely();
        }
        mDb.setTransactionSuccessful();
    } finally {
        mDb.endTransaction();
    }

    onEndTransaction();
    return numValues;
}

I cannot see the reason why you are using insert in favor of bulkInsert. Could you please clarify?

Problem Gradle fails with the following error:

Gradle sync failed: Cannot access first() element from an empty List

Solution This seems to be related a bintray-release issue that was resolved here.

Nevertheless the bintray-release used in the core project has not been updated. Using latest bintray-release version (0.4.0) solves the issue as expected.

Problem

The bulkInsert method was notifying observers for every insert into the database. This is conceptually wrong, bulk insert should only notify once, at the end of the transaction.

Solution

We now notify only once, at the end of the transaction.

Added a demo activity in the app example as well:

Hello,

I don't really know if I am something wrong,but I have a problem while reading from the migrations file. Maybe can be an encoding problem when reading using the InputStreamReader or then, when executing: SQLFile.statementsFrom(reader); I thought that probably could be malformed chars that I was getting from the server, but when updating the db (I am updating in case hashCodes of the Strings are different), that is after the migrations file is executed for first time, the string is inserted correctly. It's html content.

This is my sql script (I think that github is going to format this in html, sorry for that ):

CREATE TABLE 'faq'
    (_id INTEGER PRIMARY KEY AUTOINCREMENT, title TEXT, hash_code INTEGER);

CREATE TABLE 'faq_question'
    (_id INTEGER PRIMARY KEY AUTOINCREMENT,
    question TEXT,
    answer TEXT,
    hash_code INTEGER,
    faq_id INTEGER,
    FOREIGN KEY (faq_id) REFERENCES faq(_id) ON DELETE CASCADE);

CREATE TABLE 'about_the_brand'
    (_id INTEGER PRIMARY KEY AUTOINCREMENT,
    about TEXT,
    hash_code INTEGER);

INSERT INTO 'about_the_brand'
    (about, hash_code) VALUES ("<h2>ANOTHER WORLD LEADER</h2>\r\n\r\n<p>Since 2001, Boards & More has been marketing kites, kiteboards and\r\naccessories under the name North Kiteboarding.</p>\r\n\r\n<p>From the very beginning North Kiteboarding became a leading brand on the market thanks to both the innovative design and high quality.</p>\r\n\r\n<p>The North team strives to create pioneering and high quality products, always one step ahead at the forefront of the kiteboarding industry.</p>\r\n\r\n<p>In order to integrate the latest global trends, our products are tested and developed by our team-riders and designers at the 3 kite hot spots in Tarifa, Gorge and Hawaii.</p>\r\n\r\n<p>North Kiteboarding immediately assimilates new trends and styles, and has set new standards from the very outset, thanks to the high level of both team riders and designers. Amongst these innovations and standards are the patented Fifth-line-system, several security features as well as top-level shapes of kites and boards.</p>\r\n", -1574256766);

//////////////////////// I also attach a couple of pictures as you can see what happens first time when reading from the file, and after loading same string from the server.

I wish I had some time to research on this and solve the problem (in case it's something wrong with the read encoding) but I have to end up with a sprint, so I'll try to have a look over the weekend more deeply, but I would really appreciate if you can let me know your thoughts.

Many thanks for your time and excuse me for the inconveniences (probably I am missing something).

This PR splits ExtendedSQLiteOpenHelper into two classes: MigratingSQLiteOpenHelper and SQLiteDatabaseMetaInfo. This separates the concerns and allows to provide customized open helpers.

While splitting the class the deprecated APIs have not been moved, but removed where possible.

Tests have not been added or separated to show that all tests still pass.

This fixes #57

Allowing to specify an optional query parameter for allowing or not yieldIfContendedSafely() during bulk inserts.

The reasoning behind not wanting the yield is that in case of parallel multithreaded bulkInserts the yield will case ending and starting new transactions and thread context switching in turn causing performance issues.

In order to keep backwards compatibility and for a more flexible API, we didn't removed the yield completely, but rather let the user choose. By default, the bulkInsert will yield.

Notice the major increase of performance when not using yield:

Problem

When inserting into a table an update is tried first to provide upsert functionality. In the WHERE clause of the update, only the first column of any multi-column constraint is used.

For this table:

CREATE TABLE IF NOT EXISTS 'superhero' (
        _id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
        name TEXT NOT NULL,
        power TEXT NOT NULL,
        comic_company TEXT NOT NULL,
        UNIQUE (name, comic_company) ON CONFLICT REPLACE
);

only one entry would be allowed for each name value, when really one entry should be allowed for each combination of name and comic_company values.

Solution

Create the WHERE clause using every column in the constraint.

• Adds a Constraint class which wraps a list of column names
• Uses this class instead of a single String where needed
• Deprecates the existing methods that use String instead of Constraint

Only -1 indicates a problem according to http://d.android.com/reference/android/database/sqlite/SQLiteDatabase.html#insert(java.lang.String,%20java.lang.String,%20android.content.ContentValues)

This PR clarifies the need of SQLiteContentProviderImpl for an ExtendedSQLiteOpenHelper.

getDatabaseHelper is overwritten and returns the ExtendedSQLiteOpenHelper.