crwen comments

Repositories
Issues
Comments

Results 3 comments of


                                            crwen

optimizer: filter scan rule

It seems like that the filter is true by default, instead of null. So the solution may be like this in #795? https://github.com/risinglightdb/risinglight/blob/cd03496eb2c0cb1fab7e43fa5738d42c091013fd/src/binder/table.rs#L60-L70

Feat: Support `TopK` on `Order By ... Limit ...`

It seems that IndexScan will not be used, because the the calculated cost is `None`(`StatisticsMeta` file is not found, only `Analyze` can generate these files, but `Analyze` may have something...

Feat: Support correlated subqueries

> I think this problem is caused by `NormalizationRule`: [PushPredicateThroughJoin](https://github.com/KipData/FnckSQL/blob/main/src/optimizer/rule/normalization/pushdown_predicates.rs#L97) I don't think it would help. `Filter` is never pulled up since binding, so it won't be pushed down.