Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

nextcloud / server Public

Notifications You must be signed in to change notification settings
Fork 4.2k
Star 28.8k

Code
Issues 2.2k
Pull requests 345
Actions
Projects 1
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

fix(DB): set sharding parameters only when intended#47611

Merged

blizzz merged 4 commits intomasternextcloud/server:masterfrom fix/noid/no-sharding-32nextcloud/server:fix/noid/no-sharding-32Copy head branch name to clipboard

Aug 29, 2024

+36-19

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Aug 29, 2024

fix(DB): set sharding parameters only when intended
blizzz
committed
build: bump version to force 32bit test
blizzz
committed
fix(DB): do not assume sharding is always enabled
blizzz
committed
test(phpunit): skip sharding tests on 32bit
blizzz
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.