Hello,
I don't have much time to answer, but basic principles are these:
1. Entitystore is just for storing entity states, without other query
possibility other than entity type and/or id.
2. Indexing is for storing entity states in such way that they may be
queried using Qi4j Query API (ie something like. "give me all entities
who have MyIntProperty of their MyState type set to 23").
Hence, if you want to query entities, you have to use indexing store
to index entity states, and Qi4j API to query them. There does exist
SQL-Indexing for Qi4j, but direct queries against it are complex.
Quoting jj <[email protected]>:
Hello gents,
First of all I want to thank you for providing Qi4j – there are really some
unique ideas behind this project.
I spent the last couple of days trying to figure out the key concepts, used
patterns & principles.
To separate the state and the role-dependent behavior is from my point of
view really interesting and it matches
with my experience I collected in the projects I was involved in.
Ok, what I still not yet really is the idea how to persist the states –
means how to persist the entities.
Especially when considering the SQL Entity Storage. I tried the Postgresql
examples and realize that all the
entities in the example code are persist to a table called
“schema.qi4j-entities”.
Our domain model includes about 100-120 key entities and it would be a
pleasure to model them in the Qi4j
semantics. But the “materialized” schema – in our case the SQL schema must
reflect the model as we have e.g.
reporting tools that expects to query an SQL database. I’m not sure if I
completely miss the point but I was
somehow not able to figure the basic principle from the source code (also
due lack of time.. ). Maybe you guys
are able to give me a brief intro about the basics (SQL) persistence
concepts..
Thank you in advance.
jj
--
View this message in context:
http://qi4j-dev.23929.n6.nabble.com/SQL-Entity-Storage-Basic-Principles-tp7077.html
Sent from the Qi4j-dev mailing list archive at Nabble.com.
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
