mirror of
https://github.com/lancedb/lancedb.git
synced 2026-09-12 16:22:24 +00:00
LanceDB namespace names permit periods, so excluding them here put Secrets out of reach inside any namespace a user already has one in -- unreachable to create, alter, describe, drop or bind, with no way to recover but renaming the namespace. A period is ruled out at either end instead, which is RFC 1123's shape and Kubernetes' rule for object names. That stops `.` and `..` and anything reading as a hidden file or a path fragment in a listing or an error. Nothing in the layout depends on it -- the service encodes every segment -- so it buys legibility rather than safety, and it is free only until a name is stored. Names and path segments follow one rule: the two are joined nowhere, but a rule that held for one and not the other would be worse than either. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UfmeJ533rQDnPBkMtjerV6