Skip to content

docs(admin): clarify purpose of 64-bit database identifiers - #15481

Merged
miaulalala merged 1 commit into
masterfrom
jtr/docs-admin-db-ch-64bitIDs
Sep 1, 2026
Merged

docs(admin): clarify purpose of 64-bit database identifiers#15481
miaulalala merged 1 commit into
masterfrom
jtr/docs-admin-db-ch-64bitIDs

Conversation

@joshtrichards

Copy link
Copy Markdown
Member

☑️ Resolves

Clarify a bit why administrators may need to convert database identifiers to 64-bit integers.

Changes:

  • explains the limitations of 32-bit database identifiers
  • describes how identifier exhaustion can affect large installations
  • clarifies that 64-bit identifiers provide capacity for future growth
  • updates the chapter title to better communicate the conversion’s purpose
  • Minor wording adjustments

Follow-up ideas:

  • Symptoms

🖼️ Screenshots

✅ Checklist

  • I have built the documentation locally and reviewed the output
  • Screenshots are included for visual changes
  • I have not moved or renamed pages (or added a redirect if I did)
  • I have run codespell or similar and addressed any spelling issues

@nickvergessen
nickvergessen removed their request for review August 27, 2026 13:30
Base automatically changed from jtr/docs-admin-db-ch-ordering to master September 1, 2026 20:37
Signed-off-by: Josh <josh.t.richards@gmail.com>
@miaulalala
miaulalala force-pushed the jtr/docs-admin-db-ch-64bitIDs branch from 894a360 to ecf2922 Compare September 1, 2026 20:40
@miaulalala
miaulalala enabled auto-merge September 1, 2026 20:41
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

Last updated: Tue, 01 Sep 2026 23:59:33 GMT

@miaulalala
miaulalala merged commit 312ed6a into master Sep 1, 2026
26 checks passed
@miaulalala
miaulalala deleted the jtr/docs-admin-db-ch-64bitIDs branch September 1, 2026 23:59
@joshtrichards

Copy link
Copy Markdown
Member Author

/backport to stable35

@backportbot

backportbot Bot commented Sep 2, 2026

Copy link
Copy Markdown

The backport to stable35 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable35
git pull origin stable35

# Create the new backport branch
git checkout -b backport/15481/stable35

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick ecf29225

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/15481/stable35

Error: Failed to clone repository: Failed to create working tree: error: RPC failed; HTTP 401 curl 22 The requested URL returned error: 401
fatal: expected flush after ref listing


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@joshtrichards

Copy link
Copy Markdown
Member Author

/backport to stable34

@backportbot

backportbot Bot commented Sep 2, 2026

Copy link
Copy Markdown

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/15481/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick ecf29225

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/15481/stable34

Error: Failed to clone repository: Failed to create working tree: error: RPC failed; HTTP 401 curl 22 The requested URL returned error: 401
fatal: expected flush after ref listing


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants