Skip to content

.order_by doesn't work if query uses a FOR for binding #893

@msullivan

Description

@msullivan

This happens in some complex queries:

        from models.orm import default, std

        res = self.client.query(
            default.UserGroup.select(
                name=True,
            )
            .filter(
                lambda g: std.count(g.users.filter(lambda u: u.name_len > 5))
                >= 0
            )
            .order_by(name=True)
        )
        names = [x.name for x in res]
        self.assertEqual(names, sorted(names))

The query generated is

FOR usergroup IN default::UserGroup SELECT usergroup {
  name,
} FILTER std::count((SELECT usergroup.users FILTER .name_len > (<std::int64>$_qb_arg_0))) >= (<std::int64>$_qb_arg_1) ORDER BY .name

which doesn't work, because the ORDER BY is inside the FOR loop.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions