Search and SQL
Search opens a cited passage. SQL returns rows from table files. A question drafts one statement.
Search and SQL stay inside one drive, on what you can see. A hidden file is absent. Notes on a hidden directory are absent. Each one writes a record. Neither one writes an answer.
Search
In the command field, type and choose Search this directory or Search this drive. Search this directory covers the open directory: the files in it, notes on those files, and notes on the directory. A child directory is a separate search.
A file hit opens the file. A directory hit opens the directory. Drive keeps one hit for each, the best passage. The passage can come from the file, a note on it, or a PDF attached to a note. A picture is found from a short description when one is written.
A drive whose index has not been written yet returns no hits. A new note, an edit, or a delete joins the next index. Until that index is written, search can still show the previous text of something you may see.
A document is found from its passages and from the notes on that file. A table stays the bytes SQL reads. Search can still find it from the file name, the columns, and the rows. Measures stay out of that row text. A raster picture can gain a note that describes it. SVG and a picture over 15 MiB stay as the file.
SQL
Query appears on a directory that has a table, and on a table file you select. Tables are CSV, Parquet, and a flat JSON array.
The page names the tables a statement can use. The statement is one SELECT or one WITH. It uses those names. It does not name a path.
Files in the folder that share one shape are one table, named for the folder. A different shape stays its own table, named for the file. A child folder whose tables share one shape is one table, named for the child. A child with more than one shape is left out. A folder below that child is left out. Query on one file reads that file. The page names that relation.
Run reads the rows now. The result is a table under the editor. Drive does not add an answer.
A question
The field says Ask a question about this table, or Ask a question about these tables. Generate query writes one statement from the tables you can see, runs it, and puts the statement in the editor with the rows.
If that step is unavailable, the message is The model is not configured.
Saved queries
Saved queries sit under the editor. Save keeps the statement in the editor with this file or folder. The dialog says the rows are read when it runs. Leave Shared off and the query is yours. Turn Shared on and anyone who can query that file or folder can run it.
Open a saved query to run it. On one you saved, you can rename it, replace the statement with the one in the editor, share it or stop sharing it, or delete it. Delete removes the saved statement.
The statement rules are on SQL. The routes are on the HTTP reference.