Open sebastian opened 5 years ago
Currently we disallow using math with implicit functions. So for instance round(col/3)
is disallowed.
What I'm saying generally is that we can allow math as long as constants are not used. So we could do round(col1/col2)
. The rule that any expression with two or more math operations is treated as a constant would still apply.
As another example, for the synthetic data project, I made a nateive database view where datetime is converted to epoch (since cloak doesn't support that), and then wanted to do:
select bucket(dropoff_datetime - pickup_datetime by 100)
from syn_rides
but not allowed. This issue would allow that.
In a separate issue @yoid2000 comments that:
What should we allow? The math restrictions we have in place are in large part present because we want to prevent the construction of a boolean logic by use of arbitrary math. Then I believe it was limited further for some other reason.
What does the above statement concrete mean we could allow?
Assuming the above is fine, we would need to discuss the seeds too.