Escaping table names in SQL environment does not work.

Reported on ZenDesk.

"It appears that the ability to escape a table name in a CREATE TABLE statement has either been disabled or has suffered a bug. Escaping appears to work correctly for column names and for table names in the INSERT and SELECT statements. For example, none of the following work (but should):

CREATE TABLE [my Table1](id INTEGER);
CREATE TABLE 'my Table2' (id INTEGER);
CREATE TABLE "my Table3" (id INTEGER);
CREATE TABLE `my Table4` (id INTEGER);

Column escaping appears to be working well:
CREATE TABLE test ('my id' INTEGER);
INSERT INTO test VALUES (123);
SELECT [my id], "my id", `my id` FROM test;

The following appears as though it would work, except that it can't find the named table:
INSERT INTO [my Table1] VALUES (1);
INSERT INTO 'my Table2' VALUES (2);
SELECT \* FROM "my Table3";
SELECT \* FROM `my Table4`;"

CREATE TABLE [my Table1](id INTEGER);
CREATE TABLE 'my Table2' (id INTEGER);
CREATE TABLE "my Table3" (id INTEGER);
CREATE TABLE `my Table4` (id INTEGER);
"

It does seem to work on http://kripken.github.io/sql.js/GUI/, so it is likely an issue in our code somewhere.

No source file or test is identified in the report. Start by locating the SQL CREATE TABLE handling in the browser-based live coding environment and reproduce the four quoted table-name cases; compare with the stated column-name behavior and the sql.js GUI. Done means bracketed, single-quoted, double-quoted, and backtick-quoted table names can be created and then referenced.

Written by the indexing model from the issue text.