Skip to content
This repository was archived by the owner on May 14, 2026. It is now read-only.
This repository was archived by the owner on May 14, 2026. It is now read-only.

Wrong Composite Index Column Order #797

Closed
#798
Closed
Wrong Composite Index Column Order#797
#798
Assignees
olavloite
Labels
api: spannerIssues related to the googleapis/python-spanner-sqlalchemy API.priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Description

@waltaskew
waltaskew
opened on Nov 7, 2025

The column order for composite indexes introspected by get_multi_indexes does not match the order in the actual index.

Activity

  1. waltaskew
    added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on Nov 7, 2025
  2. blunderbuss-gcf
    assigned
    olavloite
    on Nov 7, 2025
  3. product-auto-label
    added
    api: spannerIssues related to the googleapis/python-spanner-sqlalchemy API.
    on Nov 7, 2025
  4. olavloite
    closed this as completedin #798on Nov 10, 2025
  5. olavloite
    added a commit that references this issue on Nov 10, 2025

    fix: Retrieve columns in compound indexes in correct order (#798)

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

Metadata

Metadata

Assignees

Labels

api: spannerIssues related to the googleapis/python-spanner-sqlalchemy API.priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions