[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 摘要。