Re: AQL access of fields of potential subclasses or derived archetypes

2019-05-03 Thread Thomas Beale
Hi Georg, The generic way to do this is to do what archetype tools do. An archetype itself mentioned class and attribute names from a 'reference model', but it doesn't know anything about any particular model. SUch tools have to be told to load a representation of the model in order to

Re: AQL access of fields of potential subclasses or derived archetypes

2019-05-03 Thread Seref Arikan
Bah, meant "..(I think) it should not..." On Fri, May 3, 2019 at 12:19 PM Seref Arikan < serefari...@kurumsalteknoloji.com> wrote: > As things stand, No, the spec does not allow such a thing (since it is > unspecified at the moment) and also partially No, (I don't think) it should > not allow

Re: AQL access of fields of potential subclasses or derived archetypes

2019-05-03 Thread Seref Arikan
As things stand, No, the spec does not allow such a thing (since it is unspecified at the moment) and also partially No, (I don't think) it should not allow such a thing auto-magically or try to be smart about it. As things stand, AQL has only access to information provided by the RM. I for one