Clarify how the Lookup class follow the Query Expression API.
For a class to be a lookup, it must follow the Query Expression API. **Lookup and Transform naturally follow this API.**
A Lookup is a generic class to implement lookups. A lookup is a query expression with a left-hand side, lhs; a right-hand side, rhs; and a lookup_name that is used to produce a boolean comparison between lhs and rhs such as lhs in rhs or lhs > rhs.
The notation to use a lookup in an expression is <lhs>__<lookup_name>=<rhs>.
**This class doesn’t follow the Query Expression API** since it has =<rhs> on its construction: lookups are always the end of a lookup expression.
Change History
(10)
Summary: |
Contradiction in docs/ref/models/lookups → Clarify how `Lookup` follow the Query Expression API.
|
Triage Stage: |
Unreviewed → Accepted
|
Summary: |
Clarify how `Lookup` follow the Query Expression API. → Clarify how the Lookup class follow the Query Expression API.
|
Owner: |
changed from nobody to AP Jama
|
Status: |
new → assigned
|
Cc: |
AP Jama added
|
Owner: |
AP Jama removed
|
Status: |
assigned → new
|
Owner: |
set to Caio Ariede
|
Status: |
new → assigned
|
Patch needs improvement: |
set
|
Patch needs improvement: |
unset
|
Triage Stage: |
Accepted → Ready for checkin
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
Agreed, we should clarify how the
Lookup
class follow the Query Expression API, because it implementsas_sql()
andas_vendorname()
.