Skip to content

sql: make pg_catalog error out cleanly when no cur db set #23958

Closed
#24772
Closed
sql: make pg_catalog error out cleanly when no cur db set#23958
#24772
Assignees
knz
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
@knz

Description

@knz
knz
opened on Mar 16, 2018

Currently a query on pg_catalog with no current db set fails with "no database specified".

The user would be better informed if the message would say instead "no current database set" and perhaps a hint to use set/use.

Metadata

Metadata

Assignees

Labels

C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions