Opened 7 weeks ago
Last modified 7 weeks ago
#70846 new enhancement
macports.sqlext may need patching and could have more complete usage instructions — at Version 2
Reported by: | RJVB (René Bertin) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | jmroot (Joshua Root) |
Port: | macports.sqlext |
Description (last modified by RJVB (René Bertin))
As a database n00b it wasn't exactly clear to me how to use this extension
The macports.sqlext extension provided by port:macports.sqlext no longer works, idem for the version of the code in the git master branch.
As already posted in a comment in #62365:
> port installed macports.sqlext The following ports are currently installed: macports.sqlext @2.6.3_0 (active) > sudo cp -p /opt/local/var/macports/registry/registry{,-20240920}.db > sqlite3 SQLite version 3.41.0 2023-02-21 18:09:37 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> .load /opt/local/lib/sqlite3/macports.sqlext sqlite> .open /opt/local/var/macports/registry/registry-20240920.db sqlite> VACUUM; Runtime error: no such collation sequence: VERSION
Indeed, looking at the sqlext.c code one explanation is obvious: the HAVE_SQLITE3EXT_H
macro has been replaced by SQLITE3EXT_H
(and I don't find any evidence of HAVE_SQLITE3EXT_H
being set by the build system either).
A better check would a simple #ifdef sqlite3_create_collation
but even with that change made it seems that the sqlite3_extension_init()
function is simply not being called when the extension is loaded.
Change History (3)
comment:1 Changed 7 weeks ago by RJVB (René Bertin)
Changed 7 weeks ago by RJVB (René Bertin)
Attachment: | patch-sqlext.diff added |
---|
comment:2 Changed 7 weeks ago by RJVB (René Bertin)
Description: | modified (diff) |
---|---|
Keywords: | haspatch added |
Summary: | macports.sqlext should be updated to current extension APIs → macports.sqlext may need patching and could have more complete usage instructions |
Type: | defect → enhancement |
Note: See
TracTickets for help on using
tickets.
Correction: the init function does get called, but is doesn't appear to have the intended effect:
With a bit more info printed it finally becomes clear that loading extensions only applies to already attached database(s)...
I'll attach my modifications as a patch but this ticket can be closed. Or rather, maybe only after updating the instructions for the sake of other database n00bs.