Mixing
Searching an accessor of eager-loaded relation from datatables
I've got the following models:
<?php
class User extends Model {
public function department() {
return $this->hasOne(Department::class);
}
}
class Department extends Model {
protected $appends = ["email"];
public function getEmailAttribute() {
return "$this->name@$this->domain";
}
public function user() {
return $this->belongsTo(User::class);
}
}
I'm pulling a list of users, including their departments, and showing this (using the Laravel DataTables package) in a datatable with server-side pagination/sorting/searching:
<?php
class UserController extends Controller {
public function dt() {
$users = User::with("department")
->where("location_id", session("current_location"));
return DataTables::of($users)->make();
}
}
Within the datatables setup, one of my columns is defined as follows:
{data: "department.email"}
This displays the email accessor property without issue. The problem comes when I try to search, or sort based on this column:
DataTables warning: table id=DataTables_Table_0 - Exception Message:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'departments.email' in 'where clause'
Obviously, datatables isn't aware that this is an accessor, and tries to include it in the query – with predictable results.
The only workaround I could find reference to is using the filterColumn method, which allows you to define a custom WHERE clause for a specific column. But as far as I can tell this a) requires you to define the column manually with a query builder, and b) only works on the model directly, not one of its relations.
Is there any way that I can search and sort this accessor property the same way I can with the "real" properties of the relation?
php laravel yajra-datatable laravel-datatables
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
add a comment |
I've got the following models:
<?php
class User extends Model {
public function department() {
return $this->hasOne(Department::class);
}
}
class Department extends Model {
protected $appends = ["email"];
public function getEmailAttribute() {
return "$this->name@$this->domain";
}
public function user() {
return $this->belongsTo(User::class);
}
}
I'm pulling a list of users, including their departments, and showing this (using the Laravel DataTables package) in a datatable with server-side pagination/sorting/searching:
<?php
class UserController extends Controller {
public function dt() {
$users = User::with("department")
->where("location_id", session("current_location"));
return DataTables::of($users)->make();
}
}
Within the datatables setup, one of my columns is defined as follows:
{data: "department.email"}
This displays the email accessor property without issue. The problem comes when I try to search, or sort based on this column:
DataTables warning: table id=DataTables_Table_0 - Exception Message:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'departments.email' in 'where clause'
Obviously, datatables isn't aware that this is an accessor, and tries to include it in the query – with predictable results.
The only workaround I could find reference to is using the filterColumn method, which allows you to define a custom WHERE clause for a specific column. But as far as I can tell this a) requires you to define the column manually with a query builder, and b) only works on the model directly, not one of its relations.
Is there any way that I can search and sort this accessor property the same way I can with the "real" properties of the relation?
php laravel yajra-datatable laravel-datatables
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
add a comment |
I've got the following models:
<?php
class User extends Model {
public function department() {
return $this->hasOne(Department::class);
}
}
class Department extends Model {
protected $appends = ["email"];
public function getEmailAttribute() {
return "$this->name@$this->domain";
}
public function user() {
return $this->belongsTo(User::class);
}
}
I'm pulling a list of users, including their departments, and showing this (using the Laravel DataTables package) in a datatable with server-side pagination/sorting/searching:
<?php
class UserController extends Controller {
public function dt() {
$users = User::with("department")
->where("location_id", session("current_location"));
return DataTables::of($users)->make();
}
}
Within the datatables setup, one of my columns is defined as follows:
{data: "department.email"}
This displays the email accessor property without issue. The problem comes when I try to search, or sort based on this column:
DataTables warning: table id=DataTables_Table_0 - Exception Message:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'departments.email' in 'where clause'
Obviously, datatables isn't aware that this is an accessor, and tries to include it in the query – with predictable results.
The only workaround I could find reference to is using the filterColumn method, which allows you to define a custom WHERE clause for a specific column. But as far as I can tell this a) requires you to define the column manually with a query builder, and b) only works on the model directly, not one of its relations.
Is there any way that I can search and sort this accessor property the same way I can with the "real" properties of the relation?
php laravel yajra-datatable laravel-datatables
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
I've got the following models:
<?php
class User extends Model {
public function department() {
return $this->hasOne(Department::class);
}
}
class Department extends Model {
protected $appends = ["email"];
public function getEmailAttribute() {
return "$this->name@$this->domain";
}
public function user() {
return $this->belongsTo(User::class);
}
}
I'm pulling a list of users, including their departments, and showing this (using the Laravel DataTables package) in a datatable with server-side pagination/sorting/searching:
<?php
class UserController extends Controller {
public function dt() {
$users = User::with("department")
->where("location_id", session("current_location"));
return DataTables::of($users)->make();
}
}
Within the datatables setup, one of my columns is defined as follows:
{data: "department.email"}
This displays the email accessor property without issue. The problem comes when I try to search, or sort based on this column:
DataTables warning: table id=DataTables_Table_0 - Exception Message:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'departments.email' in 'where clause'
Obviously, datatables isn't aware that this is an accessor, and tries to include it in the query – with predictable results.
The only workaround I could find reference to is using the filterColumn method, which allows you to define a custom WHERE clause for a specific column. But as far as I can tell this a) requires you to define the column manually with a query builder, and b) only works on the model directly, not one of its relations.
Is there any way that I can search and sort this accessor property the same way I can with the "real" properties of the relation?
php laravel yajra-datatable laravel-datatables
php laravel yajra-datatable laravel-datatables
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
edited Nov 20 '18 at 19:11
miken32
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
asked Nov 20 '18 at 17:18
miken32miken32
23.7k84972
23.7k84972
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You can try installing: https://github.com/babenkoivan/scout-elasticsearch-driver
This package offer possibility of defining custom rules for sql queries.
See:
- https://github.com/babenkoivan/scout-elasticsearch-driver#searchable-model
- https://github.com/babenkoivan/scout-elasticsearch-driver#search-rules
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
add a comment |
Try appending the accesor to the model.
class Department extends Model {
protected $appends = ['email'];
// the rest of your code
}
Note: Attributes in the appends array will also respect the visible and hidden settings configured on the model.
Source: Appending Values To JSON
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53398227%2fsearching-an-accessor-of-eager-loaded-relation-from-datatables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can try installing: https://github.com/babenkoivan/scout-elasticsearch-driver
This package offer possibility of defining custom rules for sql queries.
See:
- https://github.com/babenkoivan/scout-elasticsearch-driver#searchable-model
- https://github.com/babenkoivan/scout-elasticsearch-driver#search-rules
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
add a comment |
You can try installing: https://github.com/babenkoivan/scout-elasticsearch-driver
This package offer possibility of defining custom rules for sql queries.
See:
- https://github.com/babenkoivan/scout-elasticsearch-driver#searchable-model
- https://github.com/babenkoivan/scout-elasticsearch-driver#search-rules
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
add a comment |
You can try installing: https://github.com/babenkoivan/scout-elasticsearch-driver
This package offer possibility of defining custom rules for sql queries.
See:
- https://github.com/babenkoivan/scout-elasticsearch-driver#searchable-model
- https://github.com/babenkoivan/scout-elasticsearch-driver#search-rules
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
You can try installing: https://github.com/babenkoivan/scout-elasticsearch-driver
This package offer possibility of defining custom rules for sql queries.
See:
- https://github.com/babenkoivan/scout-elasticsearch-driver#searchable-model
- https://github.com/babenkoivan/scout-elasticsearch-driver#search-rules
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
answered Nov 20 '18 at 19:14
loic.lopezloic.lopez
1941113
1941113
add a comment |
add a comment |
Try appending the accesor to the model.
class Department extends Model {
protected $appends = ['email'];
// the rest of your code
}
Note: Attributes in the appends array will also respect the visible and hidden settings configured on the model.
Source: Appending Values To JSON
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
add a comment |
Try appending the accesor to the model.
class Department extends Model {
protected $appends = ['email'];
// the rest of your code
}
Note: Attributes in the appends array will also respect the visible and hidden settings configured on the model.
Source: Appending Values To JSON
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
add a comment |
Try appending the accesor to the model.
class Department extends Model {
protected $appends = ['email'];
// the rest of your code
}
Note: Attributes in the appends array will also respect the visible and hidden settings configured on the model.
Source: Appending Values To JSON
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
Try appending the accesor to the model.
class Department extends Model {
protected $appends = ['email'];
// the rest of your code
}
Note: Attributes in the appends array will also respect the visible and hidden settings configured on the model.
Source: Appending Values To JSON
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
answered Nov 20 '18 at 19:09
HCKHCK
3,50211035
3,50211035
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
add a comment |
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
It's already appended; as I said, the email shows up fine – it's just not searchable because of how Laravel Datatables treats it.
– miken32
Nov 20 '18 at 19:11
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53398227%2fsearching-an-accessor-of-eager-loaded-relation-from-datatables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
