sqlite3-ffi 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: f6057cc11c164cee5826611c884086b9b2c1e624b168bb0f141a8f0527cea6c6
+  data.tar.gz: cb0fc326b3b60ddccf66d76487397bedf3dc7af6246e97eb29812c685a089ace
+SHA512:
+  metadata.gz: e5741192faba70b8e6c18535642a14f652e9dabdb55d9279a8f4706397bf19a1f53a64dc33acd524852015d317e69c548886691b20715c07bdad91377e594dcd
+  data.tar.gz: a3a9ec82f458c9aff089fd3e555a86f6691db6e3992917eab43c2734a8b6f9dae1022c9dba4141b4111e6a1fbbc2fe23188af0b865e599988b6484c8901000aa

data/CHANGELOG.md

@@ -0,0 +1,3 @@
+## 0.1.0 (2025-04-25)
+
+- First release

data/LICENSE.txt

@@ -0,0 +1,24 @@
+Copyright (c) 2004-2024, Jamis Buck, Luis Lavena, Aaron Patterson, Mike Dalessio, et al.
+Copyright (c) 2025, Andrew Kane.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted
+provided that the following conditions are met:
+
+  1. Redistributions of source code must retain the above copyright notice, this list of conditions
+  and the following disclaimer.
+
+  2. Redistributions in binary form must reproduce the above copyright notice, this list of
+  conditions and the following disclaimer in the documentation and/or other materials provided with
+  the distribution.
+
+  3. Neither the name of the copyright holder nor the names of its contributors may be used to
+  endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
+CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
+IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
+THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.md

@@ -0,0 +1,55 @@
+# sqlite3-ffi
+
+:tada: A drop-in replacement for [sqlite3](https://github.com/sparklemotion/sqlite3-ruby) for JRuby
+
+- Passes 99% of the sqlite3 test suite
+- Works with Active Record without a custom adapter
+
+[![Build Status](https://github.com/ankane/sqlite3-ffi/actions/workflows/build.yml/badge.svg)](https://github.com/ankane/sqlite3-ffi/actions)
+
+## Installation
+
+Add this line to your Gemfile:
+
+```ruby
+gem "sqlite3-ffi"
+```
+
+And use it the exact same way as the sqlite3 gem.
+
+## Why FFI for JRuby?
+
+I tried [JDBC](https://github.com/xerial/sqlite-jdbc), [JNI](https://sqlite.org/src/dir/ext/jni), and FFI. Since SQLite is written in C, all three approaches eventually call C, but FFI provides the most compatibility.
+
+## Credits
+
+This library uses code from the [sqlite3](https://github.com/sparklemotion/sqlite3-ruby) gem and is available under the same license.
+
+The code in `lib` and `test` is an exact copy, plus some additional files:
+
+- `lib/sqlite3/ffi/*` (port of `ext`)
+- `lib/sqlite3/ffi.rb`
+- `lib/sqlite3/sqlite3_native.rb`
+- `test/ffi_helper.rb`
+
+## History
+
+View the [changelog](https://github.com/ankane/sqlite3-ffi/blob/master/CHANGELOG.md)
+
+## Contributing
+
+Everyone is encouraged to help improve this project. Here are a few ways you can help:
+
+- [Report bugs](https://github.com/ankane/sqlite3-ffi/issues)
+- Fix bugs and [submit pull requests](https://github.com/ankane/sqlite3-ffi/pulls)
+- Write, clarify, or fix documentation
+- Suggest or add new features
+
+To get started with development:
+
+```sh
+git clone https://github.com/ankane/sqlite3-ffi.git
+cd sqlite3-ffi
+bundle install
+bundle exec rake test
+```

data/lib/sqlite3/constants.rb

@@ -0,0 +1,198 @@
+module SQLite3
+  module Constants
+    #
+    # CAPI3REF: Text Encodings
+    #
+    # These constant define integer codes that represent the various
+    # text encodings supported by SQLite.
+    #
+    module TextRep
+      # IMP: R-37514-35566
+      UTF8 = 1
+      # IMP: R-03371-37637
+      UTF16LE = 2
+      # IMP: R-51971-34154
+      UTF16BE = 3
+      # Use native byte order
+      UTF16 = 4
+      # Deprecated
+      ANY = 5
+      # sqlite3_create_collation only
+      DETERMINISTIC = 0x800
+    end
+
+    #
+    # CAPI3REF: Fundamental Datatypes
+    #
+    # ^(Every value in SQLite has one of five fundamental datatypes:
+    #
+    # <ul>
+    # <li> 64-bit signed integer
+    # <li> 64-bit IEEE floating point number
+    # <li> string
+    # <li> BLOB
+    # <li> NULL
+    # </ul>)^
+    #
+    # These constants are codes for each of those types.
+    #
+    module ColumnType
+      INTEGER = 1
+      FLOAT = 2
+      TEXT = 3
+      BLOB = 4
+      NULL = 5
+    end
+
+    #
+    # CAPI3REF: Result Codes
+    #
+    # Many SQLite functions return an integer result code from the set shown
+    # here in order to indicate success or failure.
+    #
+    # New error codes may be added in future versions of SQLite.
+    #
+    module ErrorCode
+      # Successful result
+      OK = 0
+      # SQL error or missing database
+      ERROR = 1
+      # An internal logic error in SQLite
+      INTERNAL = 2
+      # Access permission denied
+      PERM = 3
+      # Callback routine requested an abort
+      ABORT = 4
+      # The database file is locked
+      BUSY = 5
+      # A table in the database is locked
+      LOCKED = 6
+      # A malloc() failed
+      NOMEM = 7
+      # Attempt to write a readonly database
+      READONLY = 8
+      # Operation terminated by sqlite_interrupt()
+      INTERRUPT = 9
+      # Some kind of disk I/O error occurred
+      IOERR = 10
+      # The database disk image is malformed
+      CORRUPT = 11
+      # (Internal Only) Table or record not found
+      NOTFOUND = 12
+      # Insertion failed because database is full
+      FULL = 13
+      # Unable to open the database file
+      CANTOPEN = 14
+      # Database lock protocol error
+      PROTOCOL = 15
+      # (Internal Only) Database table is empty
+      EMPTY = 16
+      # The database schema changed
+      SCHEMA = 17
+      # Too much data for one row of a table
+      TOOBIG = 18
+      # Abort due to constraint violation
+      CONSTRAINT = 19
+      # Data type mismatch
+      MISMATCH = 20
+      # Library used incorrectly
+      MISUSE = 21
+      # Uses OS features not supported on host
+      NOLFS = 22
+      # Authorization denied
+      AUTH = 23
+      # Not used
+      FORMAT = 24
+      # 2nd parameter to sqlite3_bind out of range
+      RANGE = 25
+      # File opened that is not a database file
+      NOTADB = 26
+      # Notifications from sqlite3_log()
+      NOTICE = 27
+      # Warnings from sqlite3_log()
+      WARNING = 28
+      # sqlite_step() has another row ready
+      ROW = 100
+      # sqlite_step() has finished executing
+      DONE = 101
+    end
+
+    #
+    # CAPI3REF: Status Parameters
+    #
+    # These integer constants designate various run-time status parameters
+    # that can be returned by SQLite3.status
+    #
+    module Status
+      # This parameter is the current amount of memory checked out using sqlite3_malloc(), either
+      # directly or indirectly. The figure includes calls made to sqlite3_malloc() by the
+      # application and internal memory usage by the SQLite library. Auxiliary page-cache memory
+      # controlled by SQLITE_CONFIG_PAGECACHE is not included in this parameter. The amount returned
+      # is the sum of the allocation sizes as reported by the xSize method in sqlite3_mem_methods.
+      MEMORY_USED = 0
+
+      # This parameter returns the number of pages used out of the pagecache memory allocator that
+      # was configured using SQLITE_CONFIG_PAGECACHE. The value returned is in pages, not in bytes.
+      PAGECACHE_USED = 1
+
+      # This parameter returns the number of bytes of page cache allocation which could not be
+      # satisfied by the SQLITE_CONFIG_PAGECACHE buffer and where forced to overflow to
+      # sqlite3_malloc(). The returned value includes allocations that overflowed because they where
+      # too large (they were larger than the "sz" parameter to SQLITE_CONFIG_PAGECACHE) and
+      # allocations that overflowed because no space was left in the page cache.
+      PAGECACHE_OVERFLOW = 2
+
+      # NOT USED
+      SCRATCH_USED = 3
+
+      # NOT USED
+      SCRATCH_OVERFLOW = 4
+
+      # This parameter records the largest memory allocation request handed to sqlite3_malloc() or
+      # sqlite3_realloc() (or their internal equivalents). Only the value returned in the
+      # *pHighwater parameter to sqlite3_status() is of interest. The value written into the
+      # *pCurrent parameter is undefined.
+      MALLOC_SIZE = 5
+
+      # The *pHighwater parameter records the deepest parser stack. The *pCurrent value is
+      # undefined. The *pHighwater value is only meaningful if SQLite is compiled with
+      # YYTRACKMAXSTACKDEPTH.
+      PARSER_STACK = 6
+
+      # This parameter records the largest memory allocation request handed to the pagecache memory
+      # allocator. Only the value returned in the *pHighwater parameter to sqlite3_status() is of
+      # interest. The value written into the *pCurrent parameter is undefined.
+      PAGECACHE_SIZE = 7
+
+      # NOT USED
+      SCRATCH_SIZE = 8
+
+      # This parameter records the number of separate memory allocations currently checked out.
+      MALLOC_COUNT = 9
+    end
+
+    module Optimize
+      # Debugging mode. Do not actually perform any optimizations but instead return one line of
+      # text for each optimization that would have been done. Off by default.
+      DEBUG = 0x00001
+
+      # Run ANALYZE on tables that might benefit. On by default.
+      ANALYZE_TABLES = 0x00002
+
+      # When running ANALYZE, set a temporary PRAGMA analysis_limit to prevent excess run-time. On
+      # by default.
+      LIMIT_ANALYZE = 0x00010
+
+      # Check the size of all tables, not just tables that have not been recently used, to see if
+      # any have grown and shrunk significantly and hence might benefit from being re-analyzed. Off
+      # by default.
+      CHECK_ALL_TABLES = 0x10000
+
+      # Useful for adding a bit to the default behavior, for example
+      #
+      #     db.optimize(Optimize::DEFAULT | Optimize::CHECK_ALL_TABLES)
+      #
+      DEFAULT = ANALYZE_TABLES | LIMIT_ANALYZE
+    end
+  end
+end