Tue, 16 Mar 2010 10:54:59 +0100 [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
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 16 Mar 2010 10:54:59 +0100] rev 4908
[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
Mon, 15 Mar 2010 18:07:54 +0100 [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
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 15 Mar 2010 18:07:54 +0100] rev 4907
[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
Mon, 15 Mar 2010 18:06:32 +0100 [rql rewriting] handle case where we want to insert snippet on a variable that has previously been moved to a subquery
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 15 Mar 2010 18:06:32 +0100] rev 4906
[rql rewriting] handle case where we want to insert snippet on a variable that has previously been moved to a subquery
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip