{"action":"created","issue":{"url":"https://api.github.com/repos/yajra/laravel-datatables/issues/150","labels_url":"https://api.github.com/repos/yajra/laravel-datatables/issues/150/labels{/name}","comments_url":"https://api.github.com/repos/yajra/laravel-datatables/issues/150/comments","events_url":"https://api.github.com/repos/yajra/laravel-datatables/issues/150/events","html_url":"https://github.com/yajra/laravel-datatables/issues/150","id":102564725,"number":150,"title":"Non-searchable column causing AJAX errors","user":{"login":"judgej","id":395934,"avatar_url":"https://avatars.githubusercontent.com/u/395934?v=3","gravatar_id":"","url":"https://api.github.com/users/judgej","html_url":"https://github.com/judgej","followers_url":"https://api.github.com/users/judgej/followers","following_url":"https://api.github.com/users/judgej/following{/other_user}","gists_url":"https://api.github.com/users/judgej/gists{/gist_id}","starred_url":"https://api.github.com/users/judgej/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/judgej/subscriptions","organizations_url":"https://api.github.com/users/judgej/orgs","repos_url":"https://api.github.com/users/judgej/repos","events_url":"https://api.github.com/users/judgej/events{/privacy}","received_events_url":"https://api.github.com/users/judgej/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-08-22T20:14:45Z","updated_at":"2015-08-24T14:46:34Z","closed_at":"2015-08-24T14:46:34Z","body":"I have use `addColumn()` to create a custom column that comes from a calculation performed outside of the database; it is just derived from an arbitrary closure. The table appears fine, the pager works, and ordering by other columns works.\r\n\r\nNow, when I try to search on the table, I get a 500 AJAX error from from the server. I'm guessing it is trying to search on that column. How do I tell the back-end not to search on that custom column, since it is not a column in the database?\r\n\r\nI was hoping it would be something simple like the `'searchable': false` flag on the front end, but I cannot see anything like that."},"comment":{"url":"https://api.github.com/repos/yajra/laravel-datatables/issues/comments/134230844","html_url":"https://github.com/yajra/laravel-datatables/issues/150#issuecomment-134230844","issue_url":"https://api.github.com/repos/yajra/laravel-datatables/issues/150","id":134230844,"user":{"login":"judgej","id":395934,"avatar_url":"https://avatars.githubusercontent.com/u/395934?v=3","gravatar_id":"","url":"https://api.github.com/users/judgej","html_url":"https://github.com/judgej","followers_url":"https://api.github.com/users/judgej/followers","following_url":"https://api.github.com/users/judgej/following{/other_user}","gists_url":"https://api.github.com/users/judgej/gists{/gist_id}","starred_url":"https://api.github.com/users/judgej/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/judgej/subscriptions","organizations_url":"https://api.github.com/users/judgej/orgs","repos_url":"https://api.github.com/users/judgej/repos","events_url":"https://api.github.com/users/judgej/events{/privacy}","received_events_url":"https://api.github.com/users/judgej/received_events","type":"User","site_admin":false},"created_at":"2015-08-24T14:46:34Z","updated_at":"2015-08-24T14:46:34Z","body":"I'll close this for now, as the front-end settings (Datatable \"options\") work for now, and I have a way forward to limit which columns are fetched at the back end. I feel like I have be revisiting some of this again, but that's for another day :smile:\r\n\r\nThanks for your help."}}