sqlite - Proposed Incompatible Changes

Not logged in

• Honeypot
• Browse
• Home
• Login
• Reports
• Search
• Ticket
• Timeline
• Wiki

• Contents
• No-Diff
• Text

*** 64,70 ****
  parts of it. It would be extremely conveniant to offer an API that
  could quickly seek to any part of the BLOB without reading the leading
  data first. It would also be faster and require less memory for the
! host application.
  
  **Database Meta Data in Virtual Tables Instead of PRAGMAs**
  
--- 64,70 ----
  parts of it. It would be extremely conveniant to offer an API that
  could quickly seek to any part of the BLOB without reading the leading
  data first. It would also be faster and require less memory for the
! host application. (Note: This item seems to have been addressed by the new sqlite3_blob_open/read/write experimental API within the same backwords compatible sqlite3 disk format. Can anyone comment on the efficiency of the disk seeks within these blobs using sqlite3_blob_read and sqlite3_blob_write's iOffset parameter - is it random access?)
  
  **Database Meta Data in Virtual Tables Instead of PRAGMAs**