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
This bug is fixed, the negation part as well as the wildcard part are
fixed in lp:zeitgeist
revno: 1470 [merge]
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Fri 2010-05-14 13:02:32 +0200
message:
Added negation
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)
** 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
2010/5/14 Markus Korn thek...@gmx.de:
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
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,
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:
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
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
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
** 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
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
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 mikkel.kamst...@gmail.com
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
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
14 matches
Mail list logo
