[spanner and sqlalchemy-spanner] Assess approaches to avoiding naming collisions.

未關閉
#18,670 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@sakthivelmanii 已經在處理了。

開始於 2026年10月13日。

評估

這個 Issue 還沒有評估資料。

描述

api: spanner type: feature request
Determine this is the right repository
  • I determined this is the correct repository in which to report this feature request.
Summary of the feature request

Recently two PRs were put forward to assist with management of Spanner Table creation and teardown in the spanner and the sqlalchemy-spanner packages and to ensure that tests do not fail due to duplicate names.

There is some discussion about whether the two are complementary OR not.
TASK: Assess the two sets of changes and identify whether the changes to sqlalchemy-spanner might mask issues with how the spanner library is expected to behave.

  • sqlalchemy-spanner PR #18623: focused on ensuring that all tables during testing are created with unique names, DDL statements are committed, and then during teardown, the teardown steps are executed, the DDL statements are committed and extra metadata is flushed to ensure that no lingering content causes any other test to fail.
  • spanner PR #18625: appears to be focused on ensuring that in unexpected situations DDL statements are not retried in production.
主要語言
Python
星號
5.4k
分支
1.8k
平均合併
2 天 7 小時
30 天內合併 PR
173

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

googleapis/google-cloud-python 的其他 Issue

查看 googleapis/google-cloud-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。