Remove support for dynamically loading extensions

Defer to the user to (statically) include the extension with the rest of
the code, and manually registering it, as described in [0].

If support for dynamic libraries and run-time dynamism in general is
desired, one shouldn't be looking for it in C or Go, who aren't the
greatest bastions of such dynamism, and instead consider more
appropriate languages, like Common Lisp or Smalltalk.

[0]: https://sqlite.org/loadext.html#statically_linking_a_run_time_loadable_extension

1 files changed, 0 insertions, 37 deletions

diff --git a/tests/functional/streq.c b/tests/functional/streq.c
deleted file mode 100644
index 70a6aa8..0000000
--- a/tests/functional/streq.c
+++ /dev/null
@@ -1,37 +0,0 @@
-#include <assert.h>
-#include <stdbool.h>
-#include <string.h>
-#include <sqlite3ext.h>
-
-
-
-SQLITE_EXTENSION_INIT1
-static void
-streq(sqlite3_context *const ctx, const int argc, sqlite3_value **const argv) {
-	assert(argc == 2);
-	const char *const str1 = (const char *)sqlite3_value_text(argv[0]);
-	const char *const str2 = (const char *)sqlite3_value_text(argv[1]);
-	const bool equal = strcmp(str1, str2) == 0;
-	const int result = equal ? 1 : 0;
-	sqlite3_result_int(ctx, result);
-}
-
-int
-sqlite3_extension_init(
-	sqlite3 *const db,
-	const char *const *const errmsg,
-	const sqlite3_api_routines *const api
-) {
-	SQLITE_EXTENSION_INIT2(api);
-	(void)errmsg;
-	return sqlite3_create_function(
-		db,
-		"streq",
-		2,
-		SQLITE_UTF8,
-		(void *)db,
-		streq,
-		NULL,
-		NULL
-	);
-}