Class A is the parent of:
- 2 Class B objects
- B1
- B2
- 2 Class C objects
- C1
- C2
- 2 Class D objects
- D1
- D2
It apears the result set returned to castor looks something like this:
+-------+-------+-------+-------+-------+
| A(p1) | A(p2) | B(id) | C(id) | D(id) |
+-------+-------+-------+-------+-------+
| Red | 42 | B1 | C1 | D1 |
| Red | 42 | B1 | C1 | D2 |
| Red | 42 | B1 | C2 | D1 |
| Red | 42 | B1 | C2 | D2 |
| Red | 42 | B2 | C1 | D1 |
| Red | 42 | B2 | C1 | D2 |
| Red | 42 | B2 | C2 | D1 |
| Red | 42 | B2 | C2 | D2 |
+-------+-------+-------+-------+-------+
Where A(p1) and A(p2) are properties of A and B(id), C(id) and D(id) are
IDs of B,C and D objects.
This works fine as long as there are only 2 of each child class.
It works decent even with 10 of each or 1000 of one type child.
With 1000 of each of A's children the system breaks down (even sooner on
most HW).
Is there any way to tell castor engine that for this particular type object
children IDs should be fetched in separate querries instead of in one go ?
Like:
+-------+-------+
| A(p1) | A(p2) |
+-------+-------+
| Red | 42 |
+-------+-------+
+-------+
| B(id) |
+-------+
| B1 |
| B2 |
+-------+
+-------+
| C(id) |
+-------+
| C1 |
| C2 |
+-------+
+-------+
| D(id) |
+-------+
| D1 |
| D2 |
+-------+
Kind Regards
Jan H. Hansen
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
