@Diego Boscá Tomás <diebo...@veratech.es> about the technology, look at this thing https://www.arangodb.com/
Search for AQL (funny name for a generic query language :P), but it seems strangely nice to be use to implement an openEHR AQL backend, since it can be used to query many backend technologies, is another abstraction layer. I'll test this thing when I have time, would love to hear from others that test it. On Fri, Oct 12, 2018 at 11:22 PM Pablo Pazos <pablo.pa...@cabolabs.com> wrote: > "impregnada" should be "implementations", damn phone auto correction :P > > That is exactly why I didn't implement AQL yet, the spec should include > syntax, behavior, semantics and result sets defined. And lots of examples > of those things combined. Because *implementations* should include > parser+engine and the parser is the simple part. Until we have that all > implementations will have differences when querying the same database. > > On Wed, Oct 10, 2018 at 4:23 PM Pablo Pazos <pablo.pa...@cabolabs.com> > wrote: > >> >> >> On Wed, Oct 10, 2018, 07:10 David Moner <dam...@gmail.com> wrote: >> >>> >>> >>> El mié., 10 oct. 2018 a las 11:52, Seref Arikan (< >>> serefari...@kurumsalteknoloji.com>) escribió: >>> >>>> >>>> Obligatory moaning for the millionth time: All of this confusion stems >>>> from lack of a formal model defining AQL semantics. I used tree pattern >>>> queries in my research so I can use those to explain aql, but as it stands >>>> the standard we have does not have this so users will keep getting >>>> confused. >>>> >>>>> >>>>> >>> This. A query language is more than just a syntax. And probably we don't >>> need to invent different behaviors than technologies that already work >>> (XPath/XQuery, for example) >>> >> >> That is exactly why I didn't implement AQL yet, the spec should include >> syntax, behavior, semantics and result sets defined. And lots of examples >> of those things combined. Because impregnada should include parser+engine >> and the parser is the simple part. Until we have that all implementations >> will have differences when querying the same database. >> >> >>> -- >>> David Moner Cano >>> >>> Web: http://www.linkedin.com/in/davidmoner >>> Twitter: @davidmoner >>> Skype: davidmoner >>> _______________________________________________ >>> openEHR-implementers mailing list >>> openEHR-implementers@lists.openehr.org >>> >>> http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org >>> >> > > -- > *Ing. Pablo Pazos Gutiérrez* > pablo.pa...@cabolabs.com > +598 99 043 145 > skype: cabolabs > Subscribe to our newsletter <http://eepurl.com/b_w_tj> > <https://cabolabs.com/> > http://www.cabolabs.com > https://cloudehrserver.com > > -- *Ing. Pablo Pazos Gutiérrez* pablo.pa...@cabolabs.com +598 99 043 145 skype: cabolabs Subscribe to our newsletter <http://eepurl.com/b_w_tj> <https://cabolabs.com/> http://www.cabolabs.com https://cloudehrserver.com
_______________________________________________ openEHR-implementers mailing list openEHR-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
