Xuwei Fu created ARROW-17408:
Summary: C++20 compile arrow get `operator==` ambiguous
Key: ARROW-17408
URL: https://issues.apache.org/jira/browse/ARROW-17408
Project: Apache Arrow
Issue Type: Bug
lidavidm commented on issue #61:
URL: https://github.com/apache/arrow-adbc/issues/61#issuecomment-1214424587
Right, and on the other hand, databases like SQLite have no reliable way to
get the info. But APIs like JDBC, Python DBAPI, and Go's database API expose
standard ways to get last ins
krlmlr commented on issue #61:
URL: https://github.com/apache/arrow-adbc/issues/61#issuecomment-1214423568
Last inserted IDs (or the results of computed columns in general, for that
matter) can be obtained with the `RETURNING` syntax for most databases, SQL
Server has `OUTPUT` . This seems
lidavidm commented on issue #61:
URL: https://github.com/apache/arrow-adbc/issues/61#issuecomment-1214419966
> Just to be sure we're on the same page:
>
> * a "query" is a single SQL string that can return a result set but
doesn't have to
>
> * a "statement" is the resu
lidavidm commented on issue #64:
URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1214418597
Thanks, I think that aligns with what I am basically assuming so far: no
concurrent access (though maybe a particular driver can relax this, e.g. Flight
SQL), but also no guarantees
zeroshade commented on issue #64:
URL: https://github.com/apache/arrow-adbc/issues/64#issuecomment-1214417469
I'll chime in from the Go database/sql package:
* A Connection Object is assumed to be Stateful and will not be used
concurrently by multiple Goroutines
* Connections have
krlmlr commented on issue #61:
URL: https://github.com/apache/arrow-adbc/issues/61#issuecomment-1214402390
Just to be sure we're on the same page:
- a "query" is a single SQL string that can return a result set but doesn't
have to
- a "statement" is the result of preparing an SQL s
