Tue, 16 Mar 2010 10:54:59 +0100 | Sylvain Thénault | [rql rewrite] until a better solution is found raise BadSchemaDefinition when two inlined relations with security on an optional variable is used, explaining how to bypass it | file | diff | annotate |
Mon, 15 Mar 2010 18:07:54 +0100 | Sylvain Thénault | [rql rewriting] handle case where we've and optional inlined relation in the original query. Also, we should append EXISTS even in subquery to avoid inserting duplicates in results | file | diff | annotate |
Mon, 18 Jan 2010 19:21:30 +0100 | Sylvain Thénault | backport stable branch | file | diff | annotate |
Thu, 07 Jan 2010 16:52:32 +0100 | Adrien Di Mascio | update copyright: welcome 2010 | file | diff | annotate |
Thu, 19 Nov 2009 12:55:47 +0100 | Sylvain Thénault | reldefsecurity branch : | file | diff | annotate |
Thu, 12 Nov 2009 12:15:19 +0100 | Sylvain Thénault | close #511810: bad rql generated when looking for vocabulary for a relation on an entity which doesn't exist (yet) | file | diff | annotate |