Incremental Blob I/O and virtual tables
So is it supported?
If not, could the doc be updated to be more explicit?
And is there any chance this could be supported in the (near) future?
Would there be a "work-around" via vtab-specific functions to emulate it?
If it is, through which virtual-table API(s) would that work?
Thanks for details on this subject. --DD
As far as I know, it is not implemented (and can't be implemented with the current virtual table module structure without "faking it"). But it is a feature I also wanted, to add such things like:
int(*xBlobOpen)(sqlite3_vtab*,int writeable,sqlite3_int64 rowid,int column,sqlite3_vblob**out,int*size); int(*xBlobClose)(sqlite3_vblob*); int(*xBlobRead)(sqlite3_vblob*,unsigned char*buf,int offset,int length); int(*xBlobWrite)(sqlite3_vblob*,const unsigned char*buf,int offset,int length);
Thanks for the support. At least I got a reply on 1 of my 3 posts...
There are a lot of other features I would want to see for virtual tables too; this is just one of them. I posted another message on this forum about my other ideas, so you can see if you have comment of it including possibly what I wrote is no good and you know how to make it better.
Please be more specific, with a link to that post.
There are many anonymous posts, narrowing the search to yours is impossible.
Thus illustrating nicely why anonymous posts should be disallowed and posters should be obliged to use a unique handle.
I think it is important that people be allowed to post anonymously.
That said, anonymous posters need to understand that their posts carry less weight, and if they make ambiguous references to earlier posts (as Anonymous did at [3acf1639fe]) then they are likely to be completely ignored.
I was hoping you were commenting on this thread's original subject.
I'm disappointed that it's again about anonymous. You're basically
the sole authority on SQLite internals and directions (and doc), and
normally quite rigorous in the doc about when something (e.g. an API)
can and cannot be used.