Mysql storage #777
Mysql storage #777
Conversation
Add a new storage type option that stores package contents in MySql along with the package metadata. Though MySql is not the best for storing large file contents, this is an alternative to storing package contents in the file system, which should be better for highly-available/distributed use cases.
|
More information about our use case. We run BaGet in multiple datacenters pointing to a MySql database. Since BaGet only supports saving package contents to the file system, we use a distributed file system to store those documents. However, distributed file systems are not perfect and sparing you the details, we think it would be better for us to store the package contents in our MySql database along with the package metadata so everything is in one place. I think this will not be an uncommon thought. |
| return provider.GetRequiredService<FileStorageService>(); | ||
| } | ||
|
|
||
| if (configuration.HasStorageType("mysql")) |
There was a problem hiding this comment.
I realized this should perhaps be "database" not "mysql". What do you think @loic-sharma?
| migrationBuilder.AlterColumn<DateTime>( | ||
| name: "RowVersion", | ||
| table: "Packages", | ||
| rowVersion: true, | ||
| nullable: true, | ||
| oldClrType: typeof(DateTime), | ||
| oldType: "timestamp(6)", | ||
| oldNullable: true) | ||
| .Annotation("MySql:ValueGenerationStrategy", MySqlValueGenerationStrategy.ComputedColumn); |
There was a problem hiding this comment.
I was tempted to remove this but I see it is in every other migration file. Do you have a preference?
1 participant
Add a new storage type option that stores package contents in MySql
along with the package metadata.
Though MySql is not the best for storing large file contents, this is an
alternative to storing package contents in the file system, which should be
better for highly-available/distributed use cases.