trew | lightweight dependency injection library for Java | Dependency Injection library

Yes, you are right with never-ending recursion.

How do we solve this problem? Can try these steps

1 . If you have used toString() in mentioned entities, remove reference of other entity from it.

2 . Can add @JsonIgnore at one side of relation which will break the chain

For Oracle you can use INSTR(field1, chr(10)) > 0

For SQL Server you can use field1 LIKE '%' + CHAR(10) + '%' or CHARINDEX(CHAR(10), field1) > 0

this doesn't refer to your instance in this line:

I've been running into the same issue. Be sure you're dealing with a Classification problem and not a Regression problem. If your target column is continuous, you might want to use http://scikit-learn.org/stable/modules/generated/sklearn.ensemble.RandomForestRegressor.html instead of RandomForestClassifier.

This will not work as you expect because of how CakePHP fetches data.

Depending how you setup your relationships what will happen is that Cake will first select the Hobbies and then do another query for Hobby Groups.

So any sorting you apply to the second query will be generally useless and lost when that data is mapped to the list of Hobbies.

So you have

SELECT hobbies....

Then another select will be issued

SELECT hooby_groups WHERE hobby_id IN [list of ids ] ORDER BY hobby_groups_id

The data from the second select will be mapped to the first one, so your order by did not do much!

Depending on what CakePHP version you are using you can do a couple of things:

1. Define the relationship to use INNER JOIN strategy so will avoid creating two SELECT statements. This way the order by cause will sort all the data as you expect. The caveat is that with INNER JOIN Hobbies that do not have any group associated will never be selected by your pagination.

2. If you are using CakePHP 2.x you could have a look at Custom Query Pagination and build the query as you need it to be for it to work.

3. If you're using CakePHP 3.x you have a query builder there and the Paginator can paginate any query, so you can do you inner joins there.

To help you out you can use the DebugKit from CakePHP to see what actual queries are being run and how tweaking this and that parameter affects how the query is being generated. You will see where the order by is applied and why it may not work.

In CakePHP 2.x you can use type to control how the joining is done. You need to use INNER

Use this attribute to decorate over order