Say we put a constraint in ‘search for’ like below
Call Date < Date Input's value
Now if we choose “ignore empty constraints” search will give all the results if “Date input” is empty. I understand this.
However, I am unclear on following scenarios:
- What happens when “Call Date” is empty in both the cases where “ignore empty constraints” is on and off?
- If “ignore empty constraints” is off and Date value is empty (in some of the records in the DB), then would we get all the results or only the results where “Call Date” is empty?
Is there an official documentation on this? From what I have read in the documentation it only talks about the scenario of “ignore constraints on and Date Input empty”, and also it only talks about “=” as the operator.
Would be grateful if someone could throw clear light on this.
Have you tried testing it yourself yet?
I know from experience that there are certain cases where there will be results shown and you’ll need to set some conditionals to switch data sources.
I have tested it myself too, and have some learnings. But problem is that some of those learnings seem very counter intuitive and I discovered only after burning fingers.
And other thing is I am keen to understand what is Bubble’s official treatment of these scenarios.
If there is no official treatment, then they can change the behaviour easily even without announcement and we won’t know. Also, what I may learn from experiments may not be complete or reliable as my case could be specific. e.g. In example above I have used date type of data type, however the behaviour could be different for a number type of data type or others; Or the behaviour I get could be applicable when amount of data is less than certain amount; Or for all you know it could behave randomly and from my experiment I learned wrong thing.
So I feel it is important to know official treatment so that we can reliably develop applications.
I totally agree that Bubble’s official documentation can be a lot more specific about how some things can or cannot work but we can say the same about learning any kind of programming language. Documentation from different sources range from too simple to too technical.
Since Bubble is pretty much it’s own language and it’s users range from new to building apps to experienced coders, perhaps the documentation team are still trying to figure out a good balance. Maybe the team can have include more technical stuff for Bubblers like yourself.
Thus why the community is a very important resource, just like all other programming language. If Stack Overflow didn’t exist programming would be less attractive to most people.
For me i will think about what i want to do, read documentation, search/ask around in the forum and then experiment until i figure out how to do things natively in Bubble. Push comes to shove and i still can’t find a native solution then i will look for plugins.
Just sharing my own thoughts
I am just saying I am keen to know what does Bubble’s documentation tell about search behaviour in different scenarios. I am not intending to get into technicalities. Just looking for answer on behaviour of tool given by Bubble.
Definitely Bubble does want to make things clear by making documentation thorough. I am just asking about some more clarity in one of the things.
Not sure how you got into native solution, plugin etc.