rename and expose sqlite3_quote_name

[riastradh-probcomp]

No description provided.

[gregory-marton]

It seems like a decent name, actually. Perhaps sql_quoted(...)?
In what sense is it not exposed?

The thing that seems hard is to remember to quote names, and to figure out which things are names and therefore need quoting and should be formatted into the query string, vs. values that bql will take care of quoting or otherwise encoding to fill in a '?' or ':name' pattern. One almost wants to make a wrapper on db.execute that tries to figure it out for you magically.

[riastradh-probcomp]

Expose: Provide in the public bayeslite module, not in the internal bayeslite.sqlite3_util module.

Rename: Names exposed in the bayeslite module are generally not specific to sqlite3 and could, in principle, be reflected in a postgresql implementation of the same API, so the lexeme sqlite3 is inappropriate here. The quotation works for SQL and BQL alike, so the lexeme sql is not entirely appropriate either.

[riastradh-probcomp]

Fixed in 2013846 (but see issue #156).

[riastradh-probcomp]

For lazy posterity: the name I chose was bql_quote_name, even though it works just as well in SQL. That fact is not terribly important.