Description
Continuing from our previous discussion in Issue #8, we are advancing with the aim to implement the where API as delineated in the proposal. The primary version accentuated on scanning solely predicated on the model name, keeping WhereClause consistently set to None.
With this next phase, our objective is to materialize the functionality of the where API as detailed in the commit.
Key Highlights
- Introduction of
WhereCondition Struct: The key in this structure is recognized as a model member key name. This is designed to facilitate the operation where model[key] == value.
Additional Context
In the preceding phase, the where API was intentionally omitted to maintain focus and ensure an efficient launch. Now, with the foundational elements established, the integration of the where API will substantially bolster our system's querying capabilities.
For an in-depth understanding and additional details of the proposal, kindly refer back to Issue #8 and the specified commit.
Description
Continuing from our previous discussion in Issue #8, we are advancing with the aim to implement the
whereAPI as delineated in the proposal. The primary version accentuated on scanning solely predicated on the model name, keepingWhereClauseconsistently set toNone.With this next phase, our objective is to materialize the functionality of the
whereAPI as detailed in the commit.Key Highlights
WhereConditionStruct: Thekeyin this structure is recognized as a model member key name. This is designed to facilitate the operation wheremodel[key] == value.Additional Context
In the preceding phase, the
whereAPI was intentionally omitted to maintain focus and ensure an efficient launch. Now, with the foundational elements established, the integration of thewhereAPI will substantially bolster our system's querying capabilities.For an in-depth understanding and additional details of the proposal, kindly refer back to Issue #8 and the specified commit.