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
{{ message }}
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.
When creating a mysql service with an extensive list of provisioning parameters we get an error as follows:
Service broker error: Error saving provision request details to database: Error 1406: Data too long for column 'request_details' at row 1. Services relying on async provisioning will not be able to complete provisioning
After a bit of investigation I found a pull request where @josephlewis42 points out the underlying issue
Some of our datatypes are suspect, like links only having space for 255 characters when the de-facto standard is ~2000 or RequestDetails which is serialized JSON being a varchar(255)
My opinion is that it doesn't make that much sense to use varchar(255) for a column that is supposed to hold json data.
We should switch the column to text in order to take the marshalled json config.
The text was updated successfully, but these errors were encountered:
When creating a mysql service with an extensive list of provisioning parameters we get an error as follows:
After a bit of investigation I found a pull request where @josephlewis42 points out the underlying issue
My opinion is that it doesn't make that much sense to use
varchar(255)
for a column that is supposed to hold json data.We should switch the column to text in order to take the marshalled json config.
The text was updated successfully, but these errors were encountered: