tursodatabase/turso

AI Summary: The user is requesting a new feature for the Turso CLI: a `.read` command. This command would allow users to execute SQL scripts from a specified file, similar to the functionality found in SQLite and DuckDB CLIs. The provided output demonstrates that the command currently does not exist and returns an 'unrecognized subcommand' error.

AI Summary: This GitHub issue reports a bug in a PR merge script where text enclosed in backticks within a PR description is completely removed during the merge process. For example, if the description contains 'Implement `foo`', the 'foo' part is dropped, leaving only 'Implement '.

AI Summary: Debug and fix a bug in the Turso Database CLI where invalid string input (unquoted identifiers) causes a panic due to a failed assertion in the `is_double_quoted_identifier` function. The fix likely involves improving input validation and handling of unquoted identifiers within SQL queries.

AI Summary: Implement two new vector functions, `subvector` and `vector_concat`, for the Turso Database, extending its vector API to allow for sub-vector extraction and concatenation of vectors.

AI Summary: Debug a bug in the Turso Database where the SUM aggregate function returns an incorrect result (0.0 instead of 44.0) when the table contains a mix of numeric and non-numeric values. The issue is highlighted by a failing SQL test case that compares Turso's output against SQLite's.

AI Summary: The task requires implementing support for the `ATTACH` command in the Turso Database, which involves modifying the VDBE layer to handle multiple databases concurrently. This necessitates a significant change to the underlying architecture, as the current implementation assumes a single pager.

AI Summary: Implement support for the `ORDER BY` clause in compound SELECT statements within the Turso Database project. This involves modifying the database engine's query processing logic to correctly handle ordering when multiple SELECT statements are combined.

AI Summary: Implement support for geospatial data types (e.g., points, polygons) within the Turso Database, including storage, indexing (potentially using spatial indexes like R-trees), and query capabilities (e.g., finding points within a radius, intersecting polygons). This would involve extending the database's SQL dialect, data structures, and query engine.

AI Summary: The Turso Database `.import` command needs to be modified to create a table if it doesn't exist before importing data from a CSV file. Currently, it silently ignores the data if the table is missing. The solution should handle the table creation robustly, potentially including error handling for cases where the CSV header doesn't match expected column names.

AI Summary: The task is to debug a Turso Database issue where the `COALESCE` function with `MIN` aggregation is returning an incorrect result and throwing "Unexpected types" errors. The issue is highlighted by a comparison with SQLite's behavior on the same SQL query. The solution involves investigating the Turso Database's implementation of `COALESCE` and `MIN` aggregation, particularly how it handles mixed data types, and correcting any inconsistencies to match SQLite's expected output.

AI Summary: The task involves removing the Tokio dependency from the Dart/Flutter bindings of the Turso Database project by modifying the Cargo.toml file to exclude unnecessary features in the `flutter_rust_bridge` and `turso_core` dependencies and then regenerating the code using `flutter_rust_bridge_codegen`. This requires familiarity with Rust, Cargo, and the Flutter toolchain.

AI Summary: Develop Swift language bindings for the Turso Database, enabling iOS developers to utilize its features and potentially improve app performance. This involves creating a Swift interface that interacts with the existing Rust implementation of Turso.

AI Summary: The task is to investigate and fix a bug in the Turso Database where parsing invalid floating-point literals results in a parse error instead of the expected behavior (truncation) observed in SQLite. This involves understanding the current parsing logic, identifying the source of the error, and modifying the code to match SQLite's handling of invalid float literals.

AI Summary: The task is to investigate why Turso Database produces an error ("column "c0" specified more than once") when executing an UPDATE statement with duplicate column assignments, while SQLite3 does not. The goal is to determine if this is a bug in Turso Database, a difference in SQL dialect interpretation, or something else, and potentially provide a fix or clarification.

AI Summary: The task is to debug and fix a bug in the Turso Database where the `INSERT ... RETURNING` statement does not return any values, unlike its SQLite counterpart. The solution requires investigating the Turso Database's implementation of the `RETURNING` clause and ensuring it correctly returns the inserted data as expected.

AI Summary: The task is to enhance the Turso Database to efficiently handle schemas containing thousands of tables. This involves testing and potentially optimizing the database's performance, particularly concerning statement preparation, to ensure it functions correctly and avoids issues reported in SQLite with similar large schemas.

AI Summary: Debug a bug in the Turso Database CLI where interrupting a long-running query with Ctrl+C causes subsequent queries to incorrectly report as 'Query Interrupted', even if the subsequent query is valid. The fix needs to prevent this false positive error reporting.