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
Currently, project filtering is case-sensitive. If a user visits https://projects.voltstro.dev/UnityWebBrowser all is good, the project page will load, but if a user visits https://projects.voltstro.dev/unitywebbrowser, VoltProjects will come back with a 404 error.
This is happening because the unique name column is what is used for getting what project a page belongs to. The name column is also currently used for display reasons.
Normally, to compare strings Case-Insensitive, you use .Equals(comparing, StringComparison.InvariantCultureIgnoreCase), but with EF, that does not work, as we need to use Collations.
Create new "display_name" column. UI will use this for displaying (as well as short_name on small screens).
Currently, project filtering is case-sensitive. If a user visits
https://projects.voltstro.dev/UnityWebBrowser
all is good, the project page will load, but if a user visitshttps://projects.voltstro.dev/unitywebbrowser
, VoltProjects will come back with a 404 error.This is happening because the unique
name
column is what is used for getting what project a page belongs to. Thename
column is also currently used for display reasons.Normally, to compare strings Case-Insensitive, you use
.Equals(comparing, StringComparison.InvariantCultureIgnoreCase)
, but with EF, that does not work, as we need to use Collations.short_name
on small screens).project_version.latest
See https://www.npgsql.org/efcore/misc/collations-and-case-sensitivity.html?tabs=data-annotationsThe text was updated successfully, but these errors were encountered: