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
It's currently possible to create a notification handler with a function name too long to fit in the key column in the notifications database table.
Recommendations of fixes, either:
Convert to TextField, on Postgres at least there's essentially no performance benefit of using a CharField with a cap over a TextField if you don't want to cap the column size.
Validate at registration time of the notification handler that the function name is short enough to fit in the database.
I think the first option is a better option, as writing the name as Python source code will naturally limit it to reasonable lengths, at which using a TextField will have essentially the same performance.
The text was updated successfully, but these errors were encountered:
It's currently possible to create a notification handler with a function name too long to fit in the
key
column in the notifications database table.Recommendations of fixes, either:
TextField
, on Postgres at least there's essentially no performance benefit of using aCharField
with a cap over aTextField
if you don't want to cap the column size.I think the first option is a better option, as writing the name as Python source code will naturally limit it to reasonable lengths, at which using a
TextField
will have essentially the same performance.The text was updated successfully, but these errors were encountered: