1. 14 Jul, 2007 1 commit
  2. 11 Jul, 2007 3 commits
  3. 09 Jul, 2007 1 commit
  4. 06 Jul, 2007 2 commits
  5. 05 Jul, 2007 3 commits
  6. 01 Jul, 2007 1 commit
  7. 29 Jun, 2007 2 commits
  8. 28 Jun, 2007 2 commits
  9. 27 Jun, 2007 4 commits
  10. 26 Jun, 2007 2 commits
  11. 25 Jun, 2007 3 commits
  12. 19 Jun, 2007 3 commits
  13. 18 Jun, 2007 1 commit
  14. 14 Jun, 2007 2 commits
  15. 13 Jun, 2007 1 commit
  16. 12 Jun, 2007 1 commit
  17. 11 Jun, 2007 2 commits
  18. 10 Jun, 2007 1 commit
  19. 07 Jun, 2007 1 commit
  20. 05 Jun, 2007 1 commit
  21. 02 Jun, 2007 1 commit
    • romanb's avatar
      Updated 2 test cases to outline two major issues with the new hydration (at... · 2e6ed4d0
      romanb authored
      Updated 2 test cases to outline two major issues with the new hydration (at least i think that it has to do with the problems):
      1) When the result set is in a custom order, components may be doubled (this already occured half a year ago though the symptoms were different (items were assigned to the wrong collection).
      2) Accessing related components that are already loaded (but empty) results in lots of extra queries. The only way to get around that is do wrap an isset() check around nearly all places before accessing a relation. This was not the case in earlier revisions though at that time an isset() was sometimes needed, too to prevent extra queries. But now it seems to be necessary everywhere.
      2e6ed4d0
  22. 01 Jun, 2007 1 commit
  23. 29 May, 2007 1 commit