Ticket #27 (enhancement)
Opened 3 years ago
Last modified 1 year ago
OUTER JOIN capability
Status: reopened
| Reported by: | fumanchu | Assigned to: | fumanchu |
|---|---|---|---|
| Priority: | major | Milestone: | 2.0 |
| Component: | Misc | Keywords: | multirecall |
| Cc: | Estimate (total hours): | 8 | |
Currently, multirecall only provides INNER JOINs. With the changes in [110], it should be possible to provide a tree to multirecall (which would include OUTER JOINs) instead of a list of classes.
Change History
12/07/05 02:13:53: Modified by fumanchu
- status changed from assigned to closed.
- resolution set to fixed.
10/06/07 01:24:19: Modified by fumanchu
- status changed from closed to reopened.
- resolution deleted.
- milestone set to 2.0.
Re-opening this until I can revisit the decision to return dummy objects instead of None. Kinda weird. Was it just to make sorting easier?
10/06/07 01:34:42: Modified by fumanchu
...or was it to mimic the behavior of DB's? It would make caches and such easier to write if None were returned, since it would fail faster than dummy objects if someone forgot about partially-null results from multirecall.
10/06/07 01:45:15: Modified by fumanchu
Aha. Support for expr(*unitrow) is pretty critical, too. So, we can't return None. But we need a code review on this issue, and the docs and comments need a lot of work.
Fixed in [119].