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
I have some table columns that are not linked to a database column. These columns are used for example to display an input field, some static text, etc. I use the null type of columns.data
However, I do not think your proposed "fix" to map a virtual column to some existing model attribute is a solution. On the contrary, it feels like a workaround for an problem that was introduced without need.
Additionally I want to add that this is another breaking change (next to #383) that was introduced in a minor release. I propose to revert this change and release a new minor version 1.4.0.
The text was updated successfully, but these errors were encountered:
also if these table columns are not linked to a database column obviously they cannot be searchable neither orderable... so IMHO this make totally sense :
I have some table columns that are not linked to a database column. These columns are used for example to display an input field, some static text, etc. I use the
null
type of columns.dataExample:
This is working with ajax-datatables-rails 1.2.0, but with newer versions I get a validation error:
I am not sure how to "fix" this error. Can you point me to the right direction to make it work again?
EDIT:
Not sure why, but somehow I missed the closed issues about this topic:
However, I do not think your proposed "fix" to map a virtual column to some existing model attribute is a solution. On the contrary, it feels like a workaround for an problem that was introduced without need.
Additionally I want to add that this is another breaking change (next to #383) that was introduced in a minor release. I propose to revert this change and release a new minor version 1.4.0.
The text was updated successfully, but these errors were encountered: