Kathi,
if feature chaining does not work correctly with one database when
chaining between two schemas, that sounds to me like a bug in app-schema
joining. I am not aware of anyone using this use-case, nor of any test
coverage.
While there is significant use of schemas in the reference data
Hi Ben,
Tried with a second schema, but it seems to forget the schema when joining.
As long as I run it without chaining the features (so removing the
feature chaining entry from the main mapping file) it works fine,
accessing the table testmain from the schema public for the main
feature,
Kathi,
I strongly recommend keeping all tables in the same database so that you
can use joining. The performance improvement becomes very large once you
have more than a small number features: you might need 1 SQL query for
1 features with joining, but 10001 SQL queries without joining,
Ben,
MANY MANY THANKS!
I've been trawling through the documentation, but hadn't found that bit
yet (still a lot to learn!)
Now to get a feeling for my options based on performance, i.e. is it
better to pack the data from all themes (working on INSPIRE stuff here)
into 1 DB to enable
Kathi,
thank you for your detailed report. I had a look through your mapping
files and they look fine. Your testing proves that they work in a single
database.
For performance, app-schema converts queries against feature-chained
types from database sources into efficient SQL, referred to as
Hi,
In the process of trying to link features from multiple INSPIRE Themes
via Feature Chaining, I’ve run into difficulties using multiple (well 2)
databases (was trying to do one database per feature type/namespace). To
clarify that it’s not a problem with my configuration I put together a
