Allow derived cursors about apsw HOT 3 CLOSED

From [email protected] on September 27, 2009 20:07:28

Came across this while browsing some issues looking for any sign of future asyncvfs
support. Is explicit support for derived classes necessary? Can't the user accomplish
the same thing by defining a class like this?:

class Foo(object):
def init(self, cur):
self._cur = _cur
def getattr(self, k):
return getattr(self.dict['_cur'], k)

They could then add or override any methods as necessary.

from apsw.

From rogerbinns on September 27, 2009 20:15:56

Asyncvfs support is already in the current codebase. If you check out the code using
Mercurial then you will have it or you can wait till the next formal release which
will be a day or two after the next SQLite release. You can read the doc http://code.google.com/p/apsw/source/browse/doc/build.rst to see how to get it
downloaded and included. There is also a page about extensions. If you email me
privately I can also send you a zip file of the current built html documentation
which is a lot easier to read (file is ~250kb). [Or you can install Sphinx and its
dependencies which is more of a pain.]

What you have listed above is simply the 'proxy' pattern. What people really want is
to be able to tell Connection what class to use for cursors. That then won't need
any modifications at places where cursors are created.

from apsw.

Derive cursors have worked for a few releases now

from apsw.