Use of proj's sqlite database about proj4j HOT 2 OPEN

If a database is required for power or ease of porting, then H2 sounds like a good way to go.

Is a hybrid approach feasible? Keep the file-based approach for simple transformations (equivalent to current), and allow optional use of the DB for more complex things?

from proj4j.

Since EPSG is about to change their model, upstream proj will have to change accordingly to reflect that, and there's nothing wrong with existing functionality here, I'd like to wait until their new database format settles before trying to figure out the best path for considering integrating it into proj4j.

In addition to trying to make sure that any database dependency is able to stay in the world of pure java, another use case I want to make sure a potential switch addresses is making sure that interaction with an internal db file works with graal native. I know that h2 has some issues, so I'll also try to look at alternatives like derby or hsqldb to figure out what minimizes side effects for graal so it's not precluded.

from proj4j.