Yes -- we actively work w/ DB/compute companies supporting Flight w/ ~ad-hoc APIs and are thinking through integration. But seen 0 with Flight SQL (and saw a ~20% lift with Turbodc vs ODBC). So curious about either Flight (ad-hoc) or Flight SQL. The blogpost made it sound like at least 2-3 WIP for Flight SQL, which would be great to learn about & track :)
For Graphistry, we 'simply' expose Arrow-over-REST APIs for streaming/batch upload+download, so no Flight needed, and that's why we didn't build Flight into the original JS Arrow lib. But as we're getting into bigger graphs / multi GPU and wanting parallel IO for DB connectors, been watching...