Hello Sisinda
Le 08/07/2017 à 12:11, Sisinda Dinusha a écrit :
> Garbage collector dependent tests failed almost always.
>
Such tests are highly sensitive to assumption on the running environment
anyway. I presume that those assumptions are wrong on the Android case.
I suggest that you delete those tests (we will rely on those tests being
executed in the Java standard environment). There is not many such tests
I think.
> I placed SQLite configurations in a seperate class
> (SQLiteConfiguration). Since we only target for SQLite, removed codes
> regarding getting database metadata from JDBC and made them to use
> SQLiteConfiguration class. I did this because, as of my knowledge,
> there is no way to get metadata programmatically without using JDBC.
>
Understood.
> Can we install the metadata tables (Create.sql) when installing EPSG
> dataset, and to the same database? Since we cannot create schemas in
> SQLite (correct me if wrong), do we have to create another database
> for metadata?
>
I think we can keep a single database for all. The original tables
published by EPSG all have a "epsg_" prefix in their name, which
simulate schema. Apache SIS replace the "epsg_" prefix by "epsg." schema
name on the fly during installation, but we can disable this replacement
(more on it below). All metadata tables also have some prefix like "CI_"
or "MD_", and the OGC/ISO specifications are designed in such a way that
those prefixes do not clash.
For making sure that the "epsg_" prefix in table names is preserved, we
just just need to make sure that ScriptRunner.isSchemaSupported is set
to false.
Martin
