I guess you'd need to use the OVERLAP function to determine the valid cases of concurrent validity.
I guess you don't get the calculated Period of Applicability (the VT) either then.
Is there a function to calculate the overlap (PA / VT) from 2 periods?
An interesting approach. Thanks for sharing.
It's unfortunate that outer joins are not supported. I'm sure there is a reason why ???
In the (outer join) views that I wish to create I would like to have the default behaviour of "Current" , but also allow "AS OF" queries.
I guess the same result is achievable with the above solution, but it makes the queries more complicated.
How have you found the performance ? You have to join to the temporal table twice, which could quite a large table.
what about TEMPORAL DATA and OUTER JOINs today on V14.10 ?
i am facing some cases of requests ending with 3610 error and crashdumps, with a stack of views on temporal tables, each view based on left outer joins ...
Thanks for all up to date information ! i couldn't find anything in docs.
If you are getting 3610, that is a SW fault and should be reported to the Teradata Global Support center. Please write an incident.