From 8e92ef6cf31e7f3c0a0eca553c15217e34c82233 Mon Sep 17 00:00:00 2001
From: gwenn <gtreguier@gmail.com>
Date: Sat, 7 May 2016 12:04:16 +0200
Subject: [PATCH] SQLite Modules cannot be destroyed.

---
 src/vtab/int_array.rs | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/vtab/int_array.rs b/src/vtab/int_array.rs
index 3a52971..79c44f9 100644
--- a/src/vtab/int_array.rs
+++ b/src/vtab/int_array.rs
@@ -25,8 +25,14 @@ pub fn create_int_array(conn: &Connection, name: &str) -> Result<Rc<RefCell<Vec<
 /// Destroy the intarray object by dropping the virtual table.
 /// If not done explicitly by the application, the virtual table will be dropped implicitly
 /// by the system when the database connection is closed.
+/// In fact, the intarray is not destroy until the connection is closed
+/// because there is no other way to destroy the associated module.
 pub fn drop_int_array(conn: &Connection, name: &str) -> Result<()> {
     conn.execute_batch(&format!("DROP TABLE temp.\"{0}\"", escape_double_quote(name)))
+    // http://www.mail-archive.com/sqlite-users%40mailinglists.sqlite.org/msg08423.html
+    // "Once a virtual table module has been created, it cannot be modified or destroyed, except by closing the database connection."
+    /*let aux: Option<()> = None;
+    conn.create_module(name, ptr::null() as *const ffi::sqlite3_module, aux)*/
 }
 
 init_module!(INT_ARRAY_MODULE,