sqlite/ext/misc
dan 7f3d20acec Fix a crash in unionvtab caused by a misconfiguration. Add other test cases
for the same.

FossilOrigin-Name: 255d6b99de2bb210c09ebee9f9481ba3d1130fda47e6e01b4cc8411d00679d09
2017-07-18 21:19:17 +00:00
..
README.md
amatch.c
anycollseq.c
carray.c
closure.c
completion.c
compress.c
csv.c
dbdump.c
eval.c
fileio.c
fuzzer.c
ieee754.c
json1.c
memvfs.c
nextchar.c
percentile.c
regexp.c
remember.c
rot13.c
scrub.c
series.c
sha1.c
shathree.c
showauth.c
spellfix.c
stmt.c
totype.c
unionvtab.c Fix a crash in unionvtab caused by a misconfiguration. Add other test cases 2017-07-18 21:19:17 +00:00
vfslog.c
vfsstat.c
vtshim.c
wholenumber.c

README.md

Miscellaneous Extensions

This folder contains a collection of smaller loadable extensions. See https://www.sqlite.org/loadext.html for instructions on how to compile and use loadable extensions. Each extension in this folder is implemented in a single file of C code.

Each source file contains a description in its header comment. See the header comments for details about each extension. Additional notes are as follows:

  • carray.c — This module implements the carray table-valued function. It is a good example of how to go about implementing a custom table-valued function.

  • dbdump.c — This is not actually a loadable extension, but rather a library that implements an approximate equivalent to the ".dump" command of the command-line shell.

  • memvfs.c — This file implements a custom VFS that stores an entire database file in a single block of RAM. It serves as a good example of how to implement a simple custom VFS.

  • rot13.c — This file implements the very simple rot13() substitution function. This file makes a good template for implementing new custom SQL functions for SQLite.

  • series.c — This is an implementation of the "generate_series" virtual table. It can make a good template for new custom virtual table implementations.

  • shathree.c — An implementation of the sha3() and sha3_query() SQL functions. The file is named "shathree.c" instead of "sha3.c" because the default entry point names in SQLite are based on the source filename with digits removed, so if we used the name "sha3.c" then the entry point would conflict with the prior "sha1.c" extension.