[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-08-06 Thread Siegfried Gevatter
** Changed in: zeitgeist Milestone: 0.3.4 => 0.4.0 ** Changed in: zeitgeist/0.3 Milestone: 0.3.4 => None ** Also affects: zeitgeist/0.4 Importance: Undecided Status: New ** Changed in: zeitgeist/0.3 Status: Fix Released => Invalid ** Changed in: zeitgeist/0.4 Importa

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-18 Thread Mikkel Kamstrup Erlandsen
Just for the record: +1 for case sensitivity. We don't wanna go down the case-insensitive route. That's for full text indexers as it's generally not as simple as that (far from it in fact). Fx. how about transliteration? For instance - does 'รป' match 'u' (apply the same logic for all unicode glyphs

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-16 Thread Markus Korn
This bug is fixed, the negation part as well as the wildcard part are fixed in lp:zeitgeist revno: 1470 [merge] committer: Markus Korn branch nick: trunk timestamp: Fri 2010-05-14 13:02:32 +0200 message: Added negation support to some

Re: [Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-14 Thread Siegfried Gevatter
2010/5/14 Markus Korn : > Please cry out loud if you think that case sensitive searches is a bad > thing. I'm crying out loud! (not really constructive, I know :P) -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received this bug notification because y

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-14 Thread Markus Korn
** Branch linked: lp:~thekorn/zeitgeist/wildcard_support -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-14 Thread Markus Korn
I've started working on the wildcard part in lp:~thekorn/zeitgeist/wildcard_support And I'm adding another constraint: searches are case sensitive. Please cry out loud if you think that case sensitive searches is a bad thing. -- Using filters (text match / exclusion / etc) https://bugs.launchpa

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-13 Thread Markus Korn
I think I got the negation part working in lp:~thekorn/zeitgeist/negation_support Before a merge, this branch needs a few more tests, I hope to work on it tomorrow early morning. After I got this branch landed I will work on the wildcard part. ** Branch unlinked: lp:~thekorn/zeitgeist/negation_s

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-13 Thread Markus Korn
I'll not support Subject.text for now, but make it easy to add this field. I mean when I look at my database for the values I've there it turns out they are very random, like title of webpages, like "Television program of 2010-05-12, 4 - 5 p.m", negation support make close to no sense for this cas

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-13 Thread Mikkel Kamstrup Erlandsen
I think it makes perfect sense what you laid out. The only thing I am considering is subject.text. I am not sure whether or not to add negation and/or prefix queries for that one... -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received this bug notifi

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-05-13 Thread Markus Korn
I will start hacking on this again today, a plan to split it into two parts. 1.) I will start with negation 2.) the next step is wildcards There are still a few open question to me: wrt 1.) * for which fields do we allow negation? - Subject.{Uri, Interpretation, Manifestation, Origin,

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2010-04-12 Thread Siegfried Gevatter
We should finally get this in with 0.3.4. (I don't think the wildcards will be a problem, btw, but will do some benchmarking next week). ** Changed in: zeitgeist/0.3 Milestone: 0.3.3 => 0.3.4 -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-12-29 Thread Markus Korn
Moved to the 0.3.2 milestone as implmentation details needs to be discussed, see the discussion on the merge proposal. ** Changed in: zeitgeist Milestone: 0.3.1 => 0.3.2 -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received this bug notification

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-12-20 Thread Markus Korn
I updated lp:~thekorn/zeitgeist/negation_switch, * it has wildcard support ('*' is used) * added logic to Event.matches_template() and Subject.matches_template() This updates add a new convention to zeitgeist: "*" in fields which support wildcard queries must be escaped as "\*" TODO: * adding

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-12-15 Thread Mikkel Kamstrup Erlandsen
> Any comments? Yes :-) We also need to support matching semantics in the Event.matches_template() method. If FindEventIds() and Event.matches_template() do not line up 100% then monitors installed with InstallMonitor() will not coincide with the Find* results. There is also the open request to

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-12-15 Thread Markus Korn
I added a negation switch, using "!" as operator to some fields in the attached branch. There is also *one* testcase, I would like to add some more before merging this, but I'm running out of time now. Any comments? ** Changed in: zeitgeist Assignee: (unassigned) => Markus Korn (thekorn)

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-12-01 Thread Siegfried Gevatter
** Changed in: zeitgeist Milestone: 0.3.0 => 0.3.1 -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Fram

Re: [Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-26 Thread Seif Lotfy
Lets push this to 0.3.1 then this is no break to the api so we can roll it out later 2009/11/26 Mikkel Kamstrup Erlandsen > Do we really want to block 0.3.0 because of this bug? I would say no, > otherwise we will ship some very untested code if we want to ship 0.3.0 > this weekend. I say defer

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-26 Thread Mikkel Kamstrup Erlandsen
Do we really want to block 0.3.0 because of this bug? I would say no, otherwise we will ship some very untested code if we want to ship 0.3.0 this weekend. I say defer to 0.3.1, it's only a micro API break. -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-24 Thread Seif Lotfy
I think the exclusion makes a lot of sense and i think the "!" would be a good indicator for exclusion. Example this would be interesting if i want to query for my last 100 events excluding those from firefox, since firefox kinda bloats everything here. I can see myself using this a lot later in re

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-20 Thread Mikkel Kamstrup Erlandsen
Sorry; in the second paragraph above I meant "... events CAN'T have a..." -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status i

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-20 Thread Mikkel Kamstrup Erlandsen
For this question to make sense you have to give a use case and explain why it is not good enough to filter out events manually in the Firefox example. For nitpicking: events can have a "title that contains zeitgeist". They can have a subject with text field containing 'zeitgeist'. If we want to m