will pick up the designated timestamp from the source table, but it won’t pick up indexes and it won’t pick up even partitioning. I’ll check whether it’s intentional and why.quick thoughts: the inner select might be more complicated than just a simple
select * from ...
. It can have an arbitrary projection, predicates, it can also include functions, aggregations, etc. So there is not always 1:1 mapping between source and target columns. I reckon the case with 1:1 mapping (=table cloning) is frequent enough to be treated as a special case. But this has to be properly evaluated. The last thing we’d want is to create additional confusion when some
create from select
queries do clone indexes & partitioning, others don’t and it’s not immediately obvious why they behave differently.