1 reply to this topic

[dabAnaedo]

The goal is simple querying, yet remain powerful with capabilities of Ralph lauren outlet
near endless sub categorization without insane DB relations and JOINS. I'm also leaning toward perhaps adapting my application to a NoSQL database in the future, this would help in implementing that.
Is category nesting as a
An object in the database would have a category field, containing the slug. Let's say there are several objects, with varying slugs in the http://www.ralphlaurenpoloes.co.uk/
Shopping > Clothing category, perhaps: "shopping-clothing-mens", "shopping-clothing-kids" and "shopping-clothing-other".
This sounds like a good idea. The only direct problem I see is that it would be difficult to rename categories. One way to solve this would be to chain the internal ID's of the categories Ralph Lauren outlet
instead of the codes.
I'd have a collection, or a dictionary, that would translate that slug into something more meaningful for end-users (for example, "shopping-clothing-womens" -> "Women's Clothing").
But, the query above worries me. would it be slow?
One more tip: if you append every category with a dash, you won't get problems if Borse louis vuitton
one abercrombie and fitch outlet
category Abercrombie and fitch outlet
has the same prefix as another like "shopping-clothing-womans-". Then you can always use StartsWith("shopping-clothing-").
Concerning the Contains, I would probably go for StartsWith. This would produce a LIKE 'shopping-clothing%' and is a lot faster with the correct index.