-
Notifications
You must be signed in to change notification settings - Fork 1k
Order on column of included table #331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, thank you for reaching out. That is not possible, but you may list the included table and include the original table and then list by the included column. I hope that helps. Alternatively you can do client side sorting (using your own JavaScript implementation). |
Then i guess i also can't filter on those columns, client side sorting and filtering is not an option, because if i use pages i can only filter one page. Thanks for the help tho, will try your first suggestion |
Yes or you can do two request, where you retrieve id's in the first and then do an "in" filter in the second. You need to combine those two results (manually) in JavaScript. Good luck! |
I'll keep this open as a feature request. |
Hey it's me.... again...i'm sorry... I do not want to download it and combine it manually, because i am using pages. Edit: table: api.php/tbl_contacts? Edit 2.0: Sorry for wasting your time and thanks for the help yesterday again. |
Sure.. no problem. Although different issues would be better in different tickets :-).
This currently not supported as there is no nesting syntax.
Don't be. I'm glad you got it working. Enjoy the software! |
You asked:
I answered:
But this is no longer true (in v2), see: https://github.com/mevdschee/php-crud-api#multiple-filters You can now combine AND and OR :-) Enjoy! |
There are no plans to support sorting on fields of included tables. |
I'll keep this open as a feature request. |
Is it possible to order a List by an includet Column?
for example:
api.php/tbl_contacts?columns=contact_id,Name,EMail,tbl_contacttype.Description&include=tbl_contacttype&order=tbl_contacttype.Description&page=1,30
The text was updated successfully, but these errors were encountered: