Closed ryzhyk closed 1 month ago
I came across this yesterday too. I was able to use the LATENESS statement extension for views to fix the problem that I had
Unfortunately I think it's unsound in this case, i.e., you cannot manually express a safe lateness bound for this view as it should be a function of the waterlines of the two inputs to the as of join
I think this is a known limitation, but I didn't find an issue for it. I believe that in this program view
v
should have a waterline.