-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
, ['Created_at', '<', Time ()-$ H*3600] #896
Comments
Here you can use it instead. I'm not sure the position of the operator would change. |
Cycle ORM used this order. What about other ORM / DB abstractions? |
Usially it is The documentation |
The reason for current operator-parameters is that there are such operators as |
I've already fixed it myself You guys don't use this kind of work Too tongue-twisting I hope to change it to the same as a normal mathematical formula It's more convenient
I've already fixed it myself You guys don't use this kind of work Too tongue-twisting I hope to change it to the same as a normal mathematical formula It's more convenient |
I'm more repulsive to the string pattern It's easy to make mistakes Because the IDE tool is not compatible with strings I don't recommend that way of writing |
We've grown up with mathematical formulas a-b=c mode You're not used to writing like that |
We've grown up with mathematical formulas a-b=c mode You're not used to writing like that |
Sure, I understand that this format isn't natural to what anyone's used to, but how to deal with, for example, the following? ['and', 'sum>10', '!is_deleted', 'is_active'] |
What steps will reproduce the problem?
What is the expected result?
The comparative operator should be placed in the middle or it will become very detouring
For example, ['Created_at', '<', Time ()-$ H*3600]
It should be more likely to change this like a mathematical formula
What do you get instead?
Additional info
The text was updated successfully, but these errors were encountered: