Hello Martin > Actually it is still possible to initialize EPSG database even from the > sis-metadata module, using java.util.ServiceLoader. Is the later class > presents on Android? Yes it's available.
> A question however is whether we want the database to be populated when > the database is created, or a little bit later when an EPSG code is > requested for the first time. SIS currently defers EPSG schema creation > as much as possible since the database could be created for other > schemas than the EPSG one, but I'm not sure it was a good idea because > it may cause a long application freeze (about 1 minute) at any time > instead than closer to startup time. Maybe it would be a good idea to > use SQLiteOpenHelper.onCreate(…) actually. I'm interested in particular > to the following paragraph in SQLiteOpenHelper documentation: > > This class makes it easy for ContentProvider implementations to > defer opening and upgrading the database until first use, to avoid > blocking application startup with long-running database upgrades. > > I have no strong opinion about whether we should use onCreate(…) or not. > What do you think? In that case, shall we try the onCreate()? However, I'm not so sure about which method works the best here. -- Sisinda
