Skip to content

Spanner: Prevents Conflict from having the same database name#4417

Closed
chemelnucfin wants to merge 1 commit intogoogleapis:masterfrom
chemelnucfin:spanner_conflict
Closed

Spanner: Prevents Conflict from having the same database name#4417
chemelnucfin wants to merge 1 commit intogoogleapis:masterfrom
chemelnucfin:spanner_conflict

Conversation

@chemelnucfin
Copy link
Copy Markdown
Contributor

Somehow this conflict occurs occasionally. I might have created another temp_db database while working on the tests.

This PR guards against it.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Nov 18, 2017
'test_read_w_index', ddl_statements=DDL_STATEMENTS + EXTRA_DDL,
pool=pool)
operation = temp_db.create()
if not temp_db.exists():

This comment was marked as spam.

@chemelnucfin
Copy link
Copy Markdown
Contributor Author

chemelnucfin commented Nov 19, 2017 via email

@chemelnucfin
Copy link
Copy Markdown
Contributor Author

Closing in favor of #4435

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants