Thanks to Richard Hipp and Hick Gunter for their replies on this topic. Given that support for support for BLOBs in virtual tables differs from that for BLOBs in physical tables, is there any method or function available to the sqlite3_xxxxx() caller that can be used to distinguish tables defined as virtual tables vs. physical tables?
Thanks in advance for any assistance provided. Randy Evans > > From: Richard Hipp <drh at sqlite.org> > > On 2/23/15, Evans, Randall <REvans at seasoft.com> wrote: > > Can the incremental BLOB functions (sqlite_blob_open(), > > sqlite_blob_read(), > > etc) access BLOB column data defined in a SQLite virtual table? If it > > matters, I am only interested in read-only access at this time. > > no. > > > > > If the answer is yes, is there any facility in virtual table support > > for xColumn or any other method that will expose to the virtual table > > module the positioning/length values supplied as the 3rd and 4th > > arguments of the > > sqlite_blob_read() function (N bytes and offset values)? > > There would have to be, in order for incremental blob I/O to be supported > on virtual tables. The absence of such a method is one reason why the > answer above is "no". > > > > > > > Randy Evans
