Re: [I] Table function supports non-literal args [datafusion]

comphead closed issue #14958: Table function supports non-literal args URL: https://github.com/apache/datafusion/issues/14958 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [I] Table function supports non-literal args [datafusion]

alamb commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2873061319 > wating for [#16015](https://github.com/apache/datafusion/pull/16015) to be merged Maybe @irenjj has some thoughts as he startes reviewing correlated subqueries -- This

Re: [I] Table function supports non-literal args [datafusion]

Lordworms commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2870484350 wating for https://github.com/apache/datafusion/pull/16015 to be merged -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [I] Table function supports non-literal args [datafusion]

Lordworms commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2777223899 Like what duckdb did ## 1. Detect Correlated Columns - Walk subquery expressions and collect all outer (correlated) column references. - Represent them as `Expr::Outer

Re: [I] Table function supports non-literal args [datafusion]

alamb commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2703669334 Thanks for the research @Lordworms FYI I personally don't likely have much time to devote to reviewing `LATERAL` / this feature. -- This is an automated message from the

Re: [I] Table function supports non-literal args [datafusion]

Lordworms commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2700016967 I have done some basic research on how Postgres deal with table function with column, for example, something like this would work in Postgresql ``` SELECT t.id, t.start_v

Re: [I] Table function supports non-literal args [datafusion]

alamb commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2699172543 I think this one is likely pretty tricky -- it might be worth working on a design / writeup at first of how it would work / what the plans would look like -- This is an automate

Re: [I] Table function supports non-literal args [datafusion]

Lordworms commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2698453390 take -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [I] Table function supports non-literal args [datafusion]

alamb commented on issue #14958: URL: https://github.com/apache/datafusion/issues/14958#issuecomment-2694202386 It might also be time to treat table functions more generally too -- so they could refer to actual columns, for example. Doing so would likely make simplifier work fall out 🤔 -

[I] Table function supports non-literal args [datafusion]

jonahgao opened a new issue, #14958: URL: https://github.com/apache/datafusion/issues/14958 ### Is your feature request related to a problem or challenge? Currently, table functions like `range` only support literal arguments. ```sh DataFusion CLI v45.0.0 > select * from range