Re: sqlite3 extensions again

["Tom Spindler (moof)" <dogcow%babymeat.com@localhost>]

> Longer term, I think the right approach is to make base sqlite3 meet the
> sqlite3 default expectations.  I remember us going around on this before
> (for json1, not rtree) and deciding we couldn't because it would be some
> kind of ABI break, and I'll try to find and read the archives.
 
In addition, the release notes for 3.36.0 say the deserialize option is
enabled by default, and it needs to be explicitly disabled. Anybody notice
any problems in the interim? If not, I'd argue that's an OK argument
against there being ABI breakage.