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
At the moment the way that querybuilder works is that it takes filters and assumes that the name maps directly to a column of the same name. This is not the case in, notably, Group where the type_string attribute is actually stored under a column called type.
The most trivial solution would be just to rename the column type_string in a migration. However a better solution would be to have a backend implementation dependent get_column method that supports mapping the filter key to the correct column in the model. This would, however, require that the concrete QueryBuilder gives the get_column more information, specifically at least the orm class Entity type.
For now, I'm just changing the relevant parts of the code (for Group) to use type instead of type_string.
The text was updated successfully, but these errors were encountered:
At the moment the way that querybuilder works is that it takes filters and assumes that the name maps directly to a column of the same name. This is not the case in, notably,
Group
where thetype_string
attribute is actually stored under a column calledtype
.The most trivial solution would be just to rename the column
type_string
in a migration. However a better solution would be to have a backend implementation dependentget_column
method that supports mapping the filter key to the correct column in the model. This would, however, require that the concreteQueryBuilder
gives theget_column
more information, specifically at least the orm class Entity type.For now, I'm just changing the relevant parts of the code (for
Group
) to usetype
instead oftype_string
.The text was updated successfully, but these errors were encountered: