> Le 24 juil. 2017 à 19:02, petern <peter.nichvolo...@gmail.com> a écrit : > > Great. But, if this is an ultimate replacement for BLOB'ed pointers, these > new pseudo-null pointers must support SQLITE_STATIC and destructor function > pointer lifetime disposition for those migrating their code.
You're right that the new APIs make pointer values unsuitable for *intermediate* values. For example, `SELECT free(use(initialize(alloc(123))))`, while possible, is out of scope. One can define such functions, but it's very risky to misuse them, leak memory, or double-free. The new pointer values indeed look *designed* so that the lifetime of pointed values is managed *outside* of any statement execution. I fail to see how blob'ed pointers did not have the exact same issue. SQLITE_STATIC and SQLITE_TRANSIENT manage the lifetime of the blob content, not of the content pointed by a blob'ed pointer. Or did I miss something? Gwendal Roué _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
