In theory APSWVFSFile can have an extra data member with a copy of the name of the inherited vfs filled in in the xOpen method and the VFSFile constructor.
The default fcntl implementation can implement the file control for SQLITE_FCNTL_VFSNAME, although there is the question about what to do if fcntl is explicitly implemented, like handling pragmas in the example code.
Since SQLITE_FCNTL_VFSNAME is a diagnostic control, it would seem to be perfectly reasonable for APSW to handle fully internally and not do any Python code callbacks.
See discussion.
In theory
APSWVFSFilecan have an extra data member with a copy of the name of the inherited vfs filled in in thexOpenmethod and theVFSFileconstructor.The default fcntl implementation can implement the file control for
SQLITE_FCNTL_VFSNAME, although there is the question about what to do if fcntl is explicitly implemented, like handling pragmas in the example code.Since SQLITE_FCNTL_VFSNAME is a diagnostic control, it would seem to be perfectly reasonable for APSW to handle fully internally and not do any Python code callbacks.
The shell
.vfsnamemethod also needs fixing.