I stumbled across a possible bug in _GenericFilter.py. All of the get_cursor
methods appear to have their param the wrong way around. This has caught me
out when I was writing code to use GenericFilter but I have not seen any
errors in the existing filter UI.
Is this a bug? and if not why is it done this way?
On Tue, 2007-01-16 at 08:48 +0000, Richard Taylor wrote:
> Is this a bug? and if not why is it done this way?
> def get_cursor(db, self):
> return db.get_person_cursor()
Looks like a typo to me. I don't think any of the existing filters
uses the cursor, that's why it has not been caught earlier. I think
the existing filters all operate on a list of handles, so the
cursor clause has not been invoked by the existing filters.
P.S. Looks like every cursor (family, source, etc) has this typo