On 26-01-16 12:39, Thomas Beale wrote:
I have not performance tested my own implementation (although I did actually build one over a decade ago). But the Informix path system was real and performant (they used a hierachical number node code approach e.g. 1.2.3, 1.2.3.1.2 etc). There are others I have read about as well, but I'd have to spend a bit of time to track them down, not having looked at it for a few years.
Interesting to research on. I think it is the best way to do it. The thing that needs to be added are the interface to create/read input/output in a developer convenient format, which reflects the RM-structure (JSON, f.e. or XML, or others, only a matter of extra interfaces)
And write an optimized AQL parser for this purpose, which is a bit difficult, but not very difficult.
Validation can happen with schematron on from path-values, constructed XML (in memory)
The whole idea is database-vendor independent, and the infrastructuring software can be written in any language/environment.
Maybe a nice project to build, after I finished the AOM in a few weeks. Thanks for sharing this Bert
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
