Wow, I think both you guys completely missed the whole point of the
post which was about hacking symfony's routing classes and
functions.
The doctrine code was just a simplified example.
The url structure was specified by the client and was not negotiable.
The url field could be copied over to a
It's basically bad solution to fetch all data and do foreach. I won't
go deep into it, just track memory usage. Doctrine records are heavy,
same for propel objects i guess.
Back to main subject. Do not separate your categories by '/'.
Make something like:
/shop/category1:subcategory:subcategory2/
I would agree. Obviously every site's requirements are different.
This works fine on my site that has about 30 categories and 100
products. Half a million categories seems like a lot, I don't even
think amazon.com has that many. If you're looking at that kind of
volume of data you're better of
> $categories=Doctrine::getTable('Category')->findAll();
> $products=Doctrine::getTable('Product')->findAll();
What if you have 500 000 records for category and even more for
products? Application will freeze computing this requests.
2009/1/8 matt marcum :
>
> Hi,
>
> I spent a little time try
