Quoting Stanislav Muhametsin <[email protected]>:
Quoting Rickard Öberg <[email protected]>:
On 2010-07-22 15.30, Stanislav Muhametsin wrote:
And the indexing generates a single table for each qualified-name. The
structure of the table depends on what type it is - property
(normal/collection/valuecomposite), asso, or multi-asso. Additionally it
has a few fixed meta-information tables, and similar-kind of table as
with ES. Currently we are working on synergy between SQL ES and SQL
Indexing - mostly by making same entity appear with same entity_pk in both.
Ok, sounds good. How are these tables kept in synch? Is the indexer
responsible for creating them?
The indexer is repsonsible for creating them. If it notices app
version change, it will wipe tables, rebuild them, and re-populate
via re-indexing. There is a way to customize that behaviour though.
Customize, as in, deciding when to do wipe&rebuild&repopulate, and
when not to (if certain app versions do not introduce any structural
entity changes).
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
