Skip to content

Document SHOW DATABASES fields that can be NULL #1562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Apr 22, 2024
Merged

Document SHOW DATABASES fields that can be NULL #1562

merged 2 commits into from
Apr 22, 2024

Conversation

@mnd999
Copy link
Contributor

@mnd999 mnd999 commented Apr 19, 2024

Some of the fields in SHOW DATABASES will always be null for databases that are not running. Update the documentation to reflect this.

@mnd999
Document SHOW DATABASES fields that can be NULL
233d772 
Some of the fields in SHOW DATABASES will always be null for databases
that are not running. Update the documentation to reflect this.
l-heemann
l-heemann approved these changes Apr 19, 2024
View reviewed changes
Copy link
Contributor

@l-heemann l-heemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what the timeline for that feature is like, but maybe we should start using "STRING NOT NULL" and such in the type column at some point 🤔

@renetapopova renetapopova added 5.20 and removed dev labels Apr 19, 2024
@neo-technology-commit-status-publisher
Copy link
Collaborator

neo-technology-commit-status-publisher commented Apr 19, 2024 •
edited
Loading

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@l-heemann l-heemann self-assigned this Apr 22, 2024
@renetapopova renetapopova merged commit 7b4d5c0 into neo4j:dev Apr 22, 2024
NataliaIvakina pushed a commit to NataliaIvakina/docs-operations that referenced this pull request May 27, 2024
@mnd999 @NataliaIvakina
Document SHOW DATABASES fields that can be NULL (neo4j#1562)
d1c9c6a 
Some of the fields in SHOW DATABASES will always be null for databases
that are not running. Update the documentation to reflect this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@l-heemann l-heemann l-heemann approved these changes

@renetapopova renetapopova renetapopova approved these changes

Assignees

@l-heemann l-heemann

Labels

5.20 team-cypher-operations

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@mnd999 @neo-technology-commit-status-publisher @l-heemann @renetapopova