Comments (6)
Notably, this goes against the filters product concept document where it says:
The order than you apply filters in does not matter. Since filters only look at the data in a single row, you can apply them in any order and end up with the same result.
from mathesar-wiki.
The order than you apply filters in does not matter. Since filters only look at the data in a single row, you can apply them in any order and end up with the same result.
I think it is pointing to the filter condition(id = 1) and not the operator that joins them. Based on what @pavish has commented on the matrix there can be only one joining operator for the whole filter set
from mathesar-wiki.
I think it is pointing to the filter condition(id = 1) and not the operator that joins them. Based on what @pavish has commented on the matrix there can be only one joining operator for the whole filter set
Yes, this is correct. What I meant was that if you have the same filters with the same operators applied, the order doesn't matter, i.e. filters are commutative.
@silentninja Where is the filter spec documentation that needs to be updated for this issue?
from mathesar-wiki.
I wrote up an architecture wiki page for filters, let's keep this updated. I haven't added anything about lexical precedence yet.
from mathesar-wiki.
If the filter API supports nested filters (which was decided) in a similar format to sqlalchemy-filters, we wouldn't have a scenario with multiple operators.
Do we need to document lexical precedence?
from mathesar-wiki.
Do we need to document lexical precedence?
I don't think so. I'll close this issue for now, we can reopen if needed.
from mathesar-wiki.
Related Issues (15)
- [Wiki] Add design toolbox section HOT 1
- Create Concepts page for data types HOT 2
- Update spec process section on wiki
- Document front end coding standards for imports HOT 5
- Document front end coding standards for `.ts` vs `.d.ts` HOT 3
- Document the structure of the backend codebase HOT 2
- There is a Japanese about page but not a home page HOT 3
- Create pages for new engineering wiki structure HOT 2
- GitHub development workflow not mentioned in contribution guidelines HOT 5
- Add a spec for import data UX.
- Style wiki using our brand colors HOT 4
- Create frontend codebase docs helping GSoC student to get on-boarded faster and independently
- Typo in the word `links` HOT 1
- Document the update process for demo servers when a new version is release HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mathesar-wiki.