--- Alexander Barkov <[EMAIL PROTECTED]> wrote:
> Actually, this limitations are for cache mode with --enable-fast-cat.
> We store category in 32 bit integer.
i suppose it's not too hard to tranlate the other strings to 32-bit
integers from php or similar and store that in for the tag or category
for cache mode.
> SQL modes can use category string with any length.
>
> >
> >
>
#######################################################################
> > #Category <string>
> > #You may distribute documents between nested categories. Category
> > #is a string in hex number notation. You may have up to 5 levels
> with
> > #256 members per level. Empty category means the root of category
> tree.
> > #Take a look into doc/categories.txt for more information.
> > #This command means a category on first level:
> > #Category AA
> > #This command meand a category on 5th level:
> > #Category FFAABBCCDD
> >
> > for categories and/or tags, why is there a limitation of depth of 5
> and
> > 2 char per depth? theoretically we should be able to use any depth
> up
> > to 256 (as that is the max number of chars for the db char field).
> >
> > some may need more entries per depth and use less depth. for
> instance
> > what if you need more than 255 entries per depth? so you would need
> to
> > use 3 chars per depth with 256/3 for the number of depths.
> >
> > if this is a string that get saved along with the url in the db,
> then
> > it shouldn't matter. we should just be able to expand the char
> field.
> > however, how is this saved in cachemode?
> >
> > this is a concern, because one of my project we cross reference
> DMOZ
> > with searchable urls. DMOZ does have more than depth of 5.
> >
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
___________________________________________
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]
