IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish: In Cloud Spanner, to create a table in Default schema, we can use only the table name to create it (example statement [1]). However to create a table in a Named Schema, we have to use “schemaName.tableName” to create it (example statement [2]).

We encountered an error while creating a table and schema with the same name (differing in capitalization only). For example, after creating a schema “account” (for example), a table with name “Account” (in Default schema) cannot be created. However it can be created in ‘account’ schema using “account.Account”.

How this might work: Tables in ‘Default’ schema should get the name default.tablename, similarly to the named schemas.

Steps to reproduce:

• Create a schema : “create schema account;”
• Creating a table : “create table Account (id int64, name string(20)) primary key(id);” fails with the error “Schema object names differ only in case: account, Account”. This is due to the rule of Spanner objects mentioned here.
• Creating a table with same name in a named schema : “create table account.Account (id int64, name string(20)) primary key(id);” creates the specified table in that specific schema “account”

If applicable, reasons why alternative solutions are not sufficient: NA

Other information (workarounds you have tried, documentation consulted, etc): NA

[1] CREATE TABLE account ( id INT64, name STRING(100) ) primary key(id) {creates a table account in Default schema}

[2] CREATE TABLE account.Account ( id INT64, name STRING(100) ) primary key(id) {creates a table Account in account schema}