In general, a very small slice of user traffic makes use of
intersections. I suspect that more complicated queries would be even
less used.

The current architecture of the system is able to retrieve subsets of
items based on the user, tag, or user/tag (arrays are constant-time
access, for you CS folk) without doing any larger fetches or reordering.
This allows for very fast performance for common activities; Fetching
bookmarks 1000-1100 is as fast as 0-100 and so on.

However, stuff like boolean query terms requires an indexing methodology
that looks a lot more like an inverted index than we currently have.
Union is somewhat doable in are current setup, but NOT (especially stuff
like a simple -term only) would be painful. I've thought about doing
/user/tag+tag+tag?any vs /user/tag+tag+tag?all or similar in the past.
Complex queries such as the ones listed are right out.

Even more so, regex search is even more difficult and is not something
we really plan to support. Although your example, you are using a
grouping operator and I'm not really sure that ordering has any meaning
for searching by tags.

Some support for this sort of things are coming, however, as we continue
to evolve our architecture.

Joshua




_____

From: ydn-delicious@yahoogroups.com
[mailto:ydn-delicious@yahoogroups.com] On Behalf Of schulzjf
Sent: Saturday, June 17, 2006 1:42 PM
To: ydn-delicious@yahoogroups.com
Subject: [ydn-delicious] Re: Boolean




I'd like to get this discussion going again.

Actually, I'd like to reopen both the Boolean and regex
discussions.

Boolean doesn't seem too hard. How about
+ AND (status quo)
- NOT
| OR

I'd love to see grouping ex: "(blog|blogs|blogging)-search" but
that
example brings us back to regexs.

"(music|mp3|audio)-articles" is more clearly focused on the
Boolean
issue.

We have a lot of intelligent people, including some Y!
decision-makers, on this list. Let's see what we can do.

Thanks,
John Schulz

--- In ydn-delicious@yahoogroups.com
<mailto:ydn-delicious%40yahoogroups.com> , "John Tropea"
<johntropea@...>
wrote:
>
> Is del.icio.us ever going to consider boolean for NOT, OR?
>
> If I were to tag stuff with both "blog" and "search"...I'd
like to see
> bookmarks just tagged "blog" but not "search"...this way I can
see my
> bookmarks that are about blogs, but not about blog search.
>
> Simpy and Raw Sugar have this, why not del.icio.us, you'd make
a lot of
> people happy...this saves me from makng a specific tag like
blog_search...at
> the moment I have these tags:
>
> blog
> search
> blog_search
>
> If del.icio.us had the NOT operator, then I wouldn't need my
"blog_search"
> tag
> ...this would be great as this type of tag isn't del.icio.us
friendly..ie.
> doesn't add quality to the emerging vocabulary
>
>
>
> --
> John Tropea
>
> Library clips
> http://libraryclips.blogsome.com
<http://libraryclips.blogsome.com>
>
> Email subscription
> http://www.feedblitz.com/f/?Sub=266
<http://www.feedblitz.com/f/?Sub=266>
> RSS subscription
> http://feeds.feedburner.com/LibraryClips
<http://feeds.feedburner.com/LibraryClips>
>
>
> [Non-text portions of this message have been removed]
>







[Non-text portions of this message have been removed]