(Copying this from Discord as suggested)

I believe the Go bindings for this use sqlite3_auto_extension, which is cool, but on Mac, I get this deprecation warning:

# github.com/asg017/sqlite-vec-go-bindings/cgo
cgo-gcc-prolog:55:11: warning: 'sqlite3_auto_extension' is deprecated: first deprecated in macOS 10.10 - Process-global auto extensions are not supported on Apple platforms [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sqlite3.h:7085:16: note: 'sqlite3_auto_extension' has been explicitly marked deprecated here
cgo-gcc-prolog:74:11: warning: 'sqlite3_cancel_auto_extension' is deprecated: first deprecated in macOS 10.14 - Process-global auto extensions are not supported on Apple platforms [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sqlite3.h:7098:16: note: 'sqlite3_cancel_auto_extension' has been explicitly marked deprecated here

@asg017 replied:

I've gotten this deprecation warning too, but the build still succeeds. So it's 1 of 2 things happening:

1. go-sqlite3 uses MacOS SQLite, and since sqlite3_auto_extension() is deprecated but not removed, the build still works, but complains. But a future version of MacOS might break this?
2. The go-sqlite3 build process references /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sqlite3.h , which causes the deprecation warning, but still uses it's bundled version of SQLite in the actual build process, which doesn't include the deprecated sqlite3_auto_extension() function and build successfully

I'm not sure which one is right, tbh. Because the MacOS SQLite also completely blocks sqlite3_load_extension(), yet go-sqlite3 can still dynamically load SQLite extensions, so # 2 seems more likely, but the Go/SQLite compilation process is complicated so I cant say for sure.

That being said, I don't like relying on sqlite3_auto_extension(). Technically, you could call sqlite3_vec_init(db, NULL, NULL) yourself in C to load the sqlite-vec extension on a database connection, and technically this could be done in Go with the ConnectHook mechanism. But when I tried last year, I got segfaults and couldn't get it to work reliably.

That being said, if the .Auto() mechanism doesnt work, or if you can't have the delcartion warnings, feel free to file and issue and I'll take another work! Just copying+pasting this message should work 💯

Which makes sense. I don't know a lot about it though.

Then, I thought:

I'm wondering, since it seems like a good idea to heed the warning at some point... is it possible to use something like this, which I did for a ulid extension in a project one time?

sql.Register("sqlite3-ulid", &sqlite3.SQLiteDriver{
    ConnectHook: func(conn *sqlite3.SQLiteConn) error {
        return conn.LoadExtension("/home/matt/Downloads/ulid0.so", "sqlite3_ulid_init")
    },
})