Improve query documentation

[ppazos]

Hi, I'm reading the documentation, just learning about MicroStream/EclipseStore, and the part that I'm mostly interested is querying capabilities. In the documentation and online video presentations there is no much info about querying. Would it be possible to demonstrate (have more tutorials available) and improve the docs on the querying area?

With this I mean querying options, alternatives, parameters, querying on complex/hierarchical objects, etc, etc.

What I'm trying to understand is how querying with MS/ES compares with a RDBMS with ORM and which is better in different scenarios.

Thanks!

[hg-ms]

Hello,

EclipseStore works differently to the most well-known databases.
When working with EclipseStore you’re working with one large java object-graph in memory instead of entities fetched from a DB, this graph is also the source of truth. Working with that object graph is just plain java independent of EclipseStore. EclipseStore is just used for persistence, not querying data. Loading data only happens at startup or if a Lazy-Reference loads data.
As the data is organized in a java object graph, querying data can be done with plain java API like java collections or e.g. Java Stream API.

[ppazos]

Hi @hg-ms thanks for the explanation.

I'm referring to this page in the documentation (https://docs.eclipsestore.io/manual/storage/queries.html), that has one little example that is also used in the MS/ES presentation I saw in YouTube. What I would like to see and learn is a more complete documentation around that subject and more examples on querying (with the stream API or with Groovy finders for instance since I use Groovy mainly) and over complex objects.

The doc also says "Of course you must care about lazy loading if you use that feature." but not sure what that means. Again, a little example there in the docs could be of great help.

Thank you.

[hg-ms]

You’re right, the note on lazy loading is quite short. The docu should be improved.

[ppazos]

@hg-ms yes, I would like to see more examples and in more complex models about querying using streams and hopefully Groovy closures via find/findAll *, and have more info about the caveats of lazy loading for querying.

• https://docs.groovy-lang.org/latest/html/groovy-jdk/java/util/Collection.html#findAll(groovy.lang.Closure)