A Query object accepts entities to query as positional arguments, so just pass it User.id:
user_id = session.query(User.id).\
filter(User.validation == request.cookies.get("validation")).\
scalar()
scalar() returns the first element of the first result or None, if no rows were found. It raises MultipleResultsFound exception for multiple rows.
load_only() indicates that only the given column-based attributes of an entity should be loaded and all others, expect the identity, will be deferred. If you do need the whole User model object later, this can be the way to go. In that case your original query has to change to:
user = session.query(User).\
filter(User.validation == request.cookies.get("validation")).\
options(load_only("id")).\
one()
one() returns exactly one result or raises an exception (0 or more than 1 result). If you accept None as a valid return value for “no user found”, use one_or_none().
Note that predicates, the criteria of the WHERE clause, should not be passed to the Query object as entities, but added with filter().
To top it off, views in Flask expect that you return one of:
- a valid response object
- a string
- a
(response, status, headers)tuple - a WSGI application
The machinery will treat anything other than a response object, a string or a tuple as a WSGI application. In your original code you returned a Query object because of the missing call to scalar() or such and this was then treated as a WSGI app.