zhjwpku commented on issue #135: URL: https://github.com/apache/iceberg-cpp/issues/135#issuecomment-3031923279
> I've used sqlpp11 before; it worked OK, but occasionally it was difficult to figure out the exact right syntax it wanted, and some things I ended up having to embed raw SQL. IMO, we'd have to evaluate whether the kinds of queries we want to write would actually work with the ORM, because if we do have to embed raw SQL, then I'd question why we don't just deal with raw SQL directly. I just took a look at iceberg-rust's SQL catalog implementation, it utilizes sqlx to support multiple backends. The use cases appear to be quite straightforward, just some prepared statements and bind execution. I also checked sqlpp23, it supports mysql/postgres/sqlite with prepared statements and bind, which seems sufficient. > > For DuckDB, this would end up as an extension right? Do extensions have to use the same C++ version as DuckDB? Not sure, duckdb extension template doesn't specify cxx standard[1], so I guess it's ok to use a different C++ version. [1] https://github.com/duckdb/extension-template/blob/main/CMakeLists.txt -- 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 unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
