67
I Use This!
Activity Not Available

Commits : Listings

Analyzed 2 months ago. based on code collected 2 months ago.
Mar 10, 2016 — Mar 10, 2017
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Fixed some typos. Anon32 More... over 12 years ago
Added win32 gem. Anon32 More... over 12 years ago
Added native-vs-dl benchmark to Rakefile. Added SQLITE3_DRIVERS environment variable to integration test to specify which driver(s) should be tested (defaults to "Native"). Anon32 More... over 12 years ago
Unit tests: done. Bugs: fixed. Anon32 More... over 12 years ago
Custom functions (aggregate and otherwise) are supported by the native driver now. Test cases for the same. Anon32 More... over 12 years ago
Added preliminary implementation of native driver (swig-based), and integration tests. Anon32 More... over 12 years ago
Some fixes to allow the DL driver to work with Ruby 1.8.1. Anon32 More... over 12 years ago
Made #quote a class method (again). Bumped version to 0.6. Anon32 More... over 12 years ago
Added check for darwin in supported platforms (thanks to bitsweat). Anon32 More... over 12 years ago
Rakefile wasn't packaging the README file. Anon32 More... over 12 years ago
Packaging now works. Added benchmarks. Anon32 More... over 12 years ago
Initial revision Anon32 More... over 12 years ago
Fixed bug in ParsedStatement that resulted in "create trigger" statements being parsed incorrectly (due to valid semicolons within the body of the statement). Incremented patch (tiny) version number. Anon32 More... over 12 years ago
Version bump reflecting minor bug-fix. Anon32 More... over 12 years ago
Fixed item #988 "Batch processing bug with trailing newline". Anon32 More... over 12 years ago
Version bump consistent with addition of new API, and backwards-compatible alterations of existing API. Anon32 More... over 12 years ago
Made Statement#execute accept bind parameters as arguments. Added Statement#execute! for returning an array of results from executing a prepared statement. Anon32 More... over 12 years ago
Applied patch from Garrett Rooney <rooneg at electricjellyfish dot net>, to clean up compiler warnings and remove unused functions and prototypes. Anon32 More... over 12 years ago
Version bump and gemspec mod in preparation for release 2.1.0. Anon32 More... over 12 years ago
static_protected_function_callback was not returning a value. Anon32 More... over 12 years ago
The pubfaq task wasn't uploading. Anon32 More... over 12 years ago
Version bump. Anon32 More... over 12 years ago
Updated test cases for changes in code (no more ":error" key, fixed problem with memory leak, etc.). Anon32 More... over 12 years ago
Errors are now always raised, instead of reported explicitly via the ":error" key in the result set. This cleaned up a lot of cruft. Anon32 More... over 12 years ago
Got rid of the whole "fragile_error" nonsense. Made better use of set_result_error now that it is working correctly. Fixed how callbacks are handled for the create_function and create_aggregate APIs. Anon32 More... over 12 years ago
It is no longer an error to finalize a finalized VM (it just silently ignores it). Fixed memory leak when reporting a MisuseException ('msg' was NULL, but was being freed). VM is now finalized automatically when an error is detected during step. Anon32 More... over 12 years ago
Added assertions to demonstrate correct behavior of Database#transaction_active? Anon32 More... over 12 years ago
Fixed stray reference to now-nonexistant Statement#execute_immediate. Anon32 More... over 12 years ago
ResultSet#initialize now invokes API::step, so that Statement#execute will execute the query. This makes doing DDL statements friendlier. Also changed Database#execute_immediate to Database#execute_batch, and Statement#execute_immediate went away. A problem with fragility in callbacks was discovered, so exceptions raised inside of a callback will only result in a warning message, not a raised exception. Likewise, using FunctionProxy#set_error can result in segmentation faults... uknown why. Anon32 More... over 12 years ago
Inspired by Copland: Rakefile is much better, version information for library is stored in its own module (which Rakefile uses directoy). Also renamed gemspec file to be the name of the project. Gem packages will now be named after the project as well, instead of "sqlite". Anon32 More... over 12 years ago