In existing systems, the user_id column has been a VARCHAR, meaning the SQL lower function is appropriate. However, if the engine is configured with user_id as a standard foreign key to a users table, this breaks:
PG::UndefinedFunction: ERROR: function lower(integer) does not exist
We can introspect on the schema to determine whether the user column should be searchable:
In existing systems, the user_id column has been a
VARCHAR
, meaning the SQLlower
function is appropriate. However, if the engine is configured withuser_id
as a standard foreign key to ausers
table, this breaks:We can introspect on the schema to determine whether the user column should be searchable:
The UI would need to reflect this too.