[Phplogcon-dev] phplogcon without user managment

[Michael Meckelein]

Google Help Center -> Advanced Search Made Easy
http://www.google.com/help/refinesearch.html

Google does not care about "AND" operator. Google include all search
terms by default. We should adapt this approach.

This means

> Okay, that sounds good, I think we should discuss the syntax:
> 
> double quote designates the search pattern
> 
> Message Contains:  "apple AND banana"

Should be equal with "apple banana", shouldn't be?

(just a site note, because it is interesting but has nothing to do with
phplogcon:
http://www.google.com/search?q=apple+AND+banana
and
http://www.google.com/search?q=apple+banana
have different result pages.)

> 
> in this search the AND is not a literal and, but a search modifier.
Search
> results will return events with both word: apple, banana
> 
> Message Contains:  "apple 'AND' banana"

We should use double quotes (") instead of single quote (') like google.
http://www.google.com/search?q=apple+%22and%22+banana

> 
> in this search the AND is a literal and, which will be included in the
> search. Search results will return messages that contain the entire
"apple
> and banana"
> 
> Same goes for OR for the above.

Ok.

> Now the slightly more complicated part
> 
> Message Contains: "red apples AND yellow bananas"
> 
> The search should be preformed as such "red AND apples AND yellow AND
> bananas" Results will display all event with those words

I would go on with this approach, because it is like Google.

> 
> Or could be preformed as such:
> 
> Message Contains: "red apples AND yellow bananas "
> 
> The search will be preformed as such " 'red apples' AND 'yellow
bananas' "
> Results will contain all events with 'red apples' AND 'yellow
bananas'.
> But
> not events like 'red delicious apples' or 'yellow delicious bananas'

If you want perform such a search you have to enclose with quotes.
http://www.google.com/search?q=%22red+apples%22+AND+%22yellow+bananas%22

Michael

> PLEASE comment on the above.
> -----
> 
> If we try to tackle the first two on the list AND/OR, we can build on
it
> from there, but changing the syntax from release to release might
confuse
> users, so we should figure out how the language is interpreted. Maybe
a
> few
> google searches to see how google interprets things might be a good
place
> to
> start.
> 
> I might be able to hack out a simple searcher tonight, nothing that
could
> be
> used in phpLogCon, but enought to show how to start processing the
search
> terms.
> 
> Brian
> 
> On 12/13/05, Rainer Gerhards <rgerhards at hq.adiscon.com> wrote:
> >
> > That sounds pretty interesting. If we can offload some work to a
> > standard library, that is helpful in many cases (assuming that the
> > library is a good one, of course ;)).
> >
> > Rainer
> >
> > > -----Original Message-----
> > > From: phplogcon-dev-bounces at lists.adiscon.com
> > > [mailto:phplogcon-dev-bounces at lists.adiscon.com] On Behalf Of
> > > Brian Shea
> > > Sent: Tuesday, December 13, 2005 1:27 AM
> > > To: phplogcon-dev at lists.adiscon.com
> > > Subject: Re: [Phplogcon-dev] phplogcon without user managment
> > >
> > > So what do you think of the 1.2.6_bgs?
> > >
> > > You can use as much/little as you want and i can help put
> > > what you need into
> > > 1.2.1/1.2.2.
> > >
> > > Also, i played with the Auth_PrefManager from PEAR, it works
> > > okay maybe that
> > > sould be considered for a futur release of phpLogCon along
> > > with PEAR:DB
> > > which works nicely.
> > >
> > > PEAR::Auth_PrefManager lacks one function
> > > Auth_PrefManager::getUserPrefs(
> > > string userId ).  Otherwise it would work great for all the
> > > Quick filters
> > > and definable filters, and maybe even supporting multiple
> > > DB's/Tables for
> > > log viewing.
> > >
> > > I'll probably write the function and email it to them.
> > >
> > > -Brian
> > >
> > > On 12/12/05, Michael Meckelein <mmeckelein at hq.adiscon.com> wrote:
> > > >
> > > > > Michael, were you having trouble with the trailing slash
> > > removal? If
> > > > so
> > > > > what
> > > > > was the problem? we should fix it to work with IIS and Apache.
> > > >
> > > > Just noticed, you have already fixed this issue in
> > > phplogcon-1.2.6_bgs
> > > > :-)
> > > >
> > > > Michael
> > > > _______________________________________________
> > > > Phplogcon-dev mailing list
> > > > http://lists.adiscon.net/mailman/listinfo/phplogcon-dev
> > > >
> > > _______________________________________________
> > > Phplogcon-dev mailing list
> > > http://lists.adiscon.net/mailman/listinfo/phplogcon-dev
> > >
> > _______________________________________________
> > Phplogcon-dev mailing list
> > http://lists.adiscon.net/mailman/listinfo/phplogcon-dev
> >
> _______________________________________________
> Phplogcon-dev mailing list
> http://lists.adiscon.net/mailman/listinfo/phplogcon-dev