Skip to content

BIGINT migrations for apps #51583

Open
Open
@ChristophWurst

Description

@ChristophWurst

How to use GitHub

  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
As a Nextcloud app developer I might run into the trouble of too big values for integer columns. Server had this issue too, so columns were migrated to BIGINT. The migration is slow and happens in a dedicated command occ db:convert-filecache-bigint. That command have a hard-coded list of tables and columns to convert. Apps have no way of using this mechanism.

Describe the solution you'd like

  1. Offer an API for apps to register columns to migrate.
  2. Have a unified setup check.
  3. Have a unified command for migration.

This can be identical to the mechanism we have to optional indices.

Describe alternatives you've considered

N/a

Additional context

N/a

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    🧭 Planning evaluation (don't pick)

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions