Windows is case insensive. Linux is case sensitive. All tables in the database are mostly small caps not causing any issues except two:
__efmigrationhistory
gradebook_configuration_progressperiod
Those on Linux require to be spelled exactly with the following upper cases otherwise things break.
__EFMigrationHistory
gradebook_configuration_progressPeriod
On a windows development machine this has no effect and all small caps still works. But a deployment to a Linux platform can break.
I am unsure of the circumstance of ending up with all small caps (either through mysql's dump/restore) or through the .NET migration but something could be refined here to avoid this cross platform development annoyance.
Windows is case insensive. Linux is case sensitive. All tables in the database are mostly small caps not causing any issues except two:
Those on Linux require to be spelled exactly with the following upper cases otherwise things break.
On a windows development machine this has no effect and all small caps still works. But a deployment to a Linux platform can break.
I am unsure of the circumstance of ending up with all small caps (either through mysql's dump/restore) or through the .NET migration but something could be refined here to avoid this cross platform development annoyance.