62dd7c25ac
Developers have been able to register custom collators using syntax like "SELECT icu_load_collation()", but collators are registered per database connection. Since we don't expose any details APIs for interacting with connection pools directly, developers can end up with flaky behavior as their queries rotate through the pool of connections, as only a subset of connections will have their collation registered. This solve this, we add a new execPerConnectionSQL() method to ensure that a given statement is executed on all current and future database connections. Bug: 152005629 Test: atest CtsDatabaseTestCases:android.database.sqlite.cts.SQLiteDatabaseTest Change-Id: I459fb7b18660d2a04eec92d1e9cc410d769e361d