Replace PostgreSQL array types with JSON serialization for MariaDB compatibility #215
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The apiserver models used PostgreSQL-specific array types (
pq.StringArray,pq.Int32Array) that are incompatible with MariaDB.Changes
Models
Frequency.Days,Frequency.Months:pq.Int32Array→[]int32AppToken.Scopes:pq.StringArray→[]stringtype:integer[]/type:text[]→serializer:json;type:jsonRepositories
github.com/lib/pqimportsconvertScopesToStringArrayto return native[]stringExample
Before:
After:
GORM's JSON serializer handles cross-database compatibility automatically, storing arrays as JSON in both MySQL/MariaDB and SQLite.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.