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
When a project is created/removed, journals will exist with the project's name being case-sensitive.
We can have journals for project ABC, and if it's been removed, project abc can be created, and previous journal lookups will show nothing for ABC, only abc.
It's helpful to have the context in admin interfaces for projects as they change over time - uncertain of other places.
We could:
change journals.name to be citext instead of text
change lower() the input and resulting value at query time
Migration to citext could have some slowdown on this table (it's got ~23 million records). We already use citext for journals.submitted_by.
Using lower() may have some query time performance issues, and we'd need to remember to use it everywhere we'd want to have those lookups be aligned.
The text was updated successfully, but these errors were encountered:
When a project is created/removed, journals will exist with the project's name being case-sensitive.
We can have journals for project
ABC
, and if it's been removed, projectabc
can be created, and previous journal lookups will show nothing forABC
, onlyabc
.It's helpful to have the context in admin interfaces for projects as they change over time - uncertain of other places.
We could:
journals.name
to becitext
instead oftext
lower()
the input and resulting value at query timeMigration to citext could have some slowdown on this table (it's got ~23 million records). We already use
citext
forjournals.submitted_by
.Using
lower()
may have some query time performance issues, and we'd need to remember to use it everywhere we'd want to have those lookups be aligned.The text was updated successfully, but these errors were encountered: