Jason Tackaberry wrote: > I added an ATTR_IGNORE_CASE flag to kaa.db. This flag can be used in > conjunction with ATTR_SEARCHABLE and ATTR_INDEXED. Case-insensitive > searches on indexed columns will still benefit from the index on that > column. > > The default behaviour remains the same: queries on columns are > case-sensitive.
Again, what is case sensitive and what not? Only keyword searches? > [EMAIL PROTECTED] ~]$ beacon --monitor --search keywords=white > Traceback (most recent call last): > File "/usr/bin/beacon", line 139, in ? > result = kaa.beacon.query(**query) > File "/usr/lib/python2.4/site-packages/kaa/beacon/__init__.py", line 83, in > query > return _client.query(**args) > File "/usr/lib/python2.4/site-packages/kaa/beacon/client.py", line 114, in > query > result = Query(self, **query) > File "/usr/lib/python2.4/site-packages/kaa/beacon/query.py", line 61, in > __init__ > self.result = self._client.database.query(**query) > File "/usr/lib/python2.4/site-packages/kaa/beacon/db.py", line 492, in query > parent = self._query_id(pid, cache) > File "/usr/lib/python2.4/site-packages/kaa/beacon/db.py", line 409, in > _query_id > i = self._db.query(type=type, id=id)[0] > IndexError: list index out of range What did you do? Please give me the full list of commands you did after you created the db. This looks like smething in the db with a missing parent. That should not happen. And do you have softlinks somewhere in that test case? > Also, another bug, I noticed that --monitor cannot be specified after > --search. I don't see a reason in bin/beacon why not. Strange. But the search parameters have to come after all parameter (a python getopt thing). So it is beacon --search --monitor keywords=foo. Dischi -- I just found out that the brain is like a computer. If that's true, then there really aren't any stupid people. Just people running Windows.
pgpz47OQ2t3OI.pgp
Description: PGP signature
