sequel-duckdb 0.2.1 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a1480a62e0835a027629de3218ef9250fea068a46f9450538de582f4b36c76be
-  data.tar.gz: 42aed3262df4e475d44b8fc55bcce43c0c141932790480554ef1fc2a6522b086
+  metadata.gz: 3e465f675eb8331927ee6bef47ac89ddf5c1b740ebe901874b57860b14d5d5d4
+  data.tar.gz: 62ca18b7870e68e85e3f557a7ff8697e59f0023659005227e257877b51e3e5b2
 SHA512:
-  metadata.gz: 48c581cb9f3d5e2fb577ac9737a357eff2ce64210f0225266a4d23bf8f1ae7c5ef2fde581e995281ff941a5f7ba75446134efc2853dc303273ee6dcbe5c16cd9
-  data.tar.gz: cbe2aaf2eb5d373e18dae14aeafe185331e8d377a06fee03f6147f50f4dc145a33f95c4338250cbd6b9826f64d30c1b3b61a621c468ae93463f50210d5dc7e63
+  metadata.gz: 2882f239ed7c4dd659c63352571d740338659a3b18a4df14bded7ecb240961cbabd89f2245eb350c4768f3ac501672d90b4b9af7243650ccf74a467d4ef8e2e9
+  data.tar.gz: 6ac18ddcefc0de413b62e83fe41650ddcda96b9fea09c361e482a6e4597443318ba8f13bd1f8f29c16452bc8065f1cff341dce95b7665d3a25a1fec1b9ecb54f

data/CHANGELOG.md

@@ -5,6 +5,16 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.3.0] - 2026-10-01
+
+### Breaking changes
+
+- Drop Ruby 3.2 support; require Ruby >= 3.3 ([9e0d2bd](https://github.com/outcomesinsights/sequel-duckdb/commit/9e0d2bda53aae129ee02773316e8c75a1142c480)): sequel-duckdb no longer installs on Ruby 3.2.
+
+### Fixed
+
+- Ship only lib/ and three docs; stop tracking the beads key ([c45dfc4](https://github.com/outcomesinsights/sequel-duckdb/commit/c45dfc4636917269f6333da1be2b21ed8855a0c2))
+
 ## [0.2.1](https://github.com/outcomesinsights/sequel-duckdb/compare/v0.2.0...v0.2.1) (2026-10-01)
 
 No changes to the gem's behaviour. The first release published by the

data/lib/sequel/duckdb/version.rb

@@ -11,6 +11,6 @@ module Sequel
     #   puts Sequel::DuckDB::VERSION
     #
     # @since 0.1.0
-    VERSION = "0.2.1"
+    VERSION = "0.3.0"
   end
 end

metadata

@@ -1,11 +1,11 @@
 --- !ruby/object:Gem::Specification
 name: sequel-duckdb
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.3.0
 platform: ruby
 authors:
 - Ryan Duryea
-bindir: exe
+bindir: bin
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
@@ -164,69 +164,15 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".beads/.beads-credential-key"
-- ".beads/.gitignore"
-- ".beads/README.md"
-- ".beads/config.yaml"
-- ".beads/hooks/post-checkout"
-- ".beads/hooks/post-merge"
-- ".beads/hooks/pre-commit"
-- ".beads/hooks/pre-push"
-- ".beads/hooks/prepare-commit-msg"
-- ".beads/metadata.json"
-- ".kiro/specs/advanced-sql-features-implementation/design.md"
-- ".kiro/specs/advanced-sql-features-implementation/requirements.md"
-- ".kiro/specs/advanced-sql-features-implementation/tasks.md"
-- ".kiro/specs/duckdb-sql-syntax-compatibility/design.md"
-- ".kiro/specs/duckdb-sql-syntax-compatibility/requirements.md"
-- ".kiro/specs/duckdb-sql-syntax-compatibility/tasks.md"
-- ".kiro/specs/edge-cases-and-validation-fixes/requirements.md"
-- ".kiro/specs/integration-test-database-setup/design.md"
-- ".kiro/specs/integration-test-database-setup/requirements.md"
-- ".kiro/specs/sequel-duckdb-adapter/design.md"
-- ".kiro/specs/sequel-duckdb-adapter/requirements.md"
-- ".kiro/specs/sequel-duckdb-adapter/tasks.md"
-- ".kiro/specs/sql-expression-handling-fix/design.md"
-- ".kiro/specs/sql-expression-handling-fix/requirements.md"
-- ".kiro/specs/sql-expression-handling-fix/tasks.md"
-- ".kiro/specs/test-infrastructure-improvements/requirements.md"
-- ".kiro/steering/product.md"
-- ".kiro/steering/structure.md"
-- ".kiro/steering/tech.md"
-- ".kiro/steering/testing.md"
-- ".mdformat.toml"
-- ".rubocop.yml"
-- ".rubocop_todo.yml"
-- ".yardopts"
-- AGENTS.md
-- API_DOCUMENTATION.md
 - CHANGELOG.md
-- FINAL_STATUS.md
 - LICENSE
-- MIGRATION_EXAMPLES.md
-- PERFORMANCE_OPTIMIZATIONS.md
 - README.md
-- REFACTORING_SUMMARY.md
-- Rakefile
-- TASK_10.2_IMPLEMENTATION_SUMMARY.md
-- docs/DUCKDB_SQL_PATTERNS.md
-- docs/TASK_12_VERIFICATION_SUMMARY.md
-- justfile
 - lib/sequel/adapters/duckdb.rb
 - lib/sequel/adapters/shared/duckdb.rb
 - lib/sequel/duckdb.rb
 - lib/sequel/duckdb/helpers/copier.rb
 - lib/sequel/duckdb/helpers/pathifier.rb
 - lib/sequel/duckdb/version.rb
-- plans/date_arithmetic.md
-- plans/engineering/Sequel.md
-- plans/engineering/duckdb.md
-- plans/engineering/sqlite.md
-- plans/mock_connection_bug.md
-- plans/mock_without_driver_gem.md
-- plans/over_engineering_analysis.md
-- plans/schema_management.md
-- sig/sequel/duckdb.rbs
 homepage: https://github.com/sequel/sequel-duckdb
 licenses:
 - MIT
@@ -242,7 +188,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 3.2.0
+      version: 3.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="

data/.beads/.beads-credential-key

@@ -1 +0,0 @@
-�:I>����G��O�FԤ�L1	s<j�,

data/.beads/.gitignore

@@ -1,66 +0,0 @@
-# Dolt database (managed by Dolt, not git)
-dolt/
-dolt-access.lock
-
-# Runtime files
-bd.sock
-bd.sock.startlock
-sync-state.json
-last-touched
-.exclusive-lock
-
-# Daemon runtime (lock, log, pid)
-daemon.*
-
-# Interactions log (runtime, not versioned)
-interactions.jsonl
-
-# Push state (runtime, per-machine)
-push-state.json
-
-# Lock files (various runtime locks)
-*.lock
-
-# Local version tracking (prevents upgrade notification spam after git ops)
-.local_version
-
-# Worktree redirect file (contains relative path to main repo's .beads/)
-# Must not be committed as paths would be wrong in other clones
-redirect
-
-# Sync state (local-only, per-machine)
-# These files are machine-specific and should not be shared across clones
-.sync.lock
-export-state/
-
-# Ephemeral store (SQLite - wisps/molecules, intentionally not versioned)
-ephemeral.sqlite3
-ephemeral.sqlite3-journal
-ephemeral.sqlite3-wal
-ephemeral.sqlite3-shm
-
-# Dolt server management (auto-started by bd)
-dolt-server.pid
-dolt-server.log
-dolt-server.lock
-dolt-server.port
-
-# Corrupt backup directories (created by bd doctor --fix recovery)
-*.corrupt.backup/
-
-# Backup data (auto-exported JSONL, local-only)
-backup/
-
-# Legacy files (from pre-Dolt versions)
-*.db
-*.db?*
-*.db-journal
-*.db-wal
-*.db-shm
-db.sqlite
-bd.db
-# NOTE: Do NOT add negation patterns here.
-# They would override fork protection in .git/info/exclude.
-# Config files (metadata.json, config.yaml) are tracked by git by default
-# since no pattern above ignores them.
-.beads-credential-key

data/.beads/README.md

@@ -1,85 +0,0 @@
-# Beads - AI-Native Issue Tracking
-
-Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
-
-## What is Beads?
-
-Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
-
-**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
-
-## Quick Start
-
-### Essential Commands
-
-```bash
-# Create new issues
-bd create "Add user authentication"
-
-# View all issues
-bd list
-
-# View issue details
-bd show <issue-id>
-
-# Update issue status
-bd update <issue-id> --claim
-bd update <issue-id> --status done
-
-# Sync with Dolt remote
-bd dolt push
-```
-
-### Working with Issues
-
-Issues in Beads are:
-
-- **Git-native**: Stored in Dolt database with version control and branching
-- **AI-friendly**: CLI-first design works perfectly with AI coding agents
-- **Branch-aware**: Issues can follow your branch workflow
-- **Always in sync**: Auto-syncs with your commits
-
-## Why Beads?
-
-✨ **AI-Native Design**
-
-- Built specifically for AI-assisted development workflows
-- CLI-first interface works seamlessly with AI coding agents
-- No context switching to web UIs
-
-🚀 **Developer Focused**
-
-- Issues live in your repo, right next to your code
-- Works offline, syncs when you push
-- Fast, lightweight, and stays out of your way
-
-🔧 **Git Integration**
-
-- Automatic sync with git commits
-- Branch-aware issue tracking
-- Dolt-native three-way merge resolution
-
-## Get Started with Beads
-
-Try Beads in your own projects:
-
-```bash
-# Install Beads
-curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
-
-# Initialize in your repo
-bd init
-
-# Create your first issue
-bd create "Try out Beads"
-```
-
-## Learn More
-
-- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
-- **Quick Start Guide**: Run `bd quickstart`
-- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
-
-______________________________________________________________________
-
-*Beads: Issue tracking that moves at the speed of thought* ⚡

data/.beads/config.yaml

@@ -1,56 +0,0 @@
-# Beads Configuration File
-# This file configures default behavior for all bd commands in this repository
-# All settings can also be set via environment variables (BD_* prefix)
-# or overridden with command-line flags
-
-# Issue prefix for this repository (used by bd init)
-# If not set, bd init will auto-detect from directory name
-# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
-# issue-prefix: ""
-
-# Use no-db mode: JSONL-only, no Dolt database
-# When true, bd will use .beads/issues.jsonl as the source of truth
-# no-db: false
-
-# Enable JSON output by default
-# json: false
-
-# Feedback title formatting for mutating commands (create/update/close/dep/edit)
-# 0 = hide titles, N > 0 = truncate to N characters
-# output:
-#   title-length: 255
-
-# Default actor for audit trails (overridden by BD_ACTOR or --actor)
-# actor: ""
-
-# Export events (audit trail) to .beads/events.jsonl on each flush/sync
-# When enabled, new events are appended incrementally using a high-water mark.
-# Use 'bd export --events' to trigger manually regardless of this setting.
-# events-export: false
-
-# Multi-repo configuration (experimental - bd-307)
-# Allows hydrating from multiple repositories and routing writes to the correct database
-# repos:
-#   primary: "."  # Primary repo (where this database lives)
-#   additional:   # Additional repos to hydrate from (read-only)
-#     - ~/beads-planning  # Personal planning repo
-#     - ~/work-planning   # Work planning repo
-
-# JSONL backup (periodic export for off-machine recovery)
-# Auto-enabled when a git remote exists. Override explicitly:
-# backup:
-#   enabled: false     # Disable auto-backup entirely
-#   interval: 15m      # Minimum time between auto-exports
-#   git-push: false    # Disable git push (export locally only)
-#   git-repo: ""       # Separate git repo for backups (default: project repo)
-
-# Integration settings (access with 'bd config get/set')
-# These are stored in the database, not in this file:
-# - jira.url
-# - jira.project
-# - linear.url
-# - linear.api-key
-# - github.org
-# - github.repo
-
-sync.remote: "git+ssh://git@github.com/outcomesinsights/sequel-duckdb.git"

data/.beads/hooks/post-checkout

@@ -1,24 +0,0 @@
-#!/usr/bin/env sh
-# --- BEGIN BEADS INTEGRATION v0.61.0 ---
-# This section is managed by beads. Do not remove these markers.
-if command -v bd >/dev/null 2>&1; then
-  export BD_GIT_HOOK=1
-  _bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
-  if command -v timeout >/dev/null 2>&1; then
-    timeout "$_bd_timeout" bd hooks run post-checkout "$@"
-    _bd_exit=$?
-    if [ $_bd_exit -eq 124 ]; then
-      echo >&2 "beads: hook 'post-checkout' timed out after ${_bd_timeout}s — continuing without beads"
-      _bd_exit=0
-    fi
-  else
-    bd hooks run post-checkout "$@"
-    _bd_exit=$?
-  fi
-  if [ $_bd_exit -eq 3 ]; then
-    echo >&2 "beads: database not initialized — skipping hook 'post-checkout'"
-    _bd_exit=0
-  fi
-  if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
-fi
-# --- END BEADS INTEGRATION v0.61.0 ---

data/.beads/hooks/post-merge

@@ -1,24 +0,0 @@
-#!/usr/bin/env sh
-# --- BEGIN BEADS INTEGRATION v0.61.0 ---
-# This section is managed by beads. Do not remove these markers.
-if command -v bd >/dev/null 2>&1; then
-  export BD_GIT_HOOK=1
-  _bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
-  if command -v timeout >/dev/null 2>&1; then
-    timeout "$_bd_timeout" bd hooks run post-merge "$@"
-    _bd_exit=$?
-    if [ $_bd_exit -eq 124 ]; then
-      echo >&2 "beads: hook 'post-merge' timed out after ${_bd_timeout}s — continuing without beads"
-      _bd_exit=0
-    fi
-  else
-    bd hooks run post-merge "$@"
-    _bd_exit=$?
-  fi
-  if [ $_bd_exit -eq 3 ]; then
-    echo >&2 "beads: database not initialized — skipping hook 'post-merge'"
-    _bd_exit=0
-  fi
-  if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
-fi
-# --- END BEADS INTEGRATION v0.61.0 ---

data/.beads/hooks/pre-commit

@@ -1,24 +0,0 @@
-#!/usr/bin/env sh
-# --- BEGIN BEADS INTEGRATION v0.61.0 ---
-# This section is managed by beads. Do not remove these markers.
-if command -v bd >/dev/null 2>&1; then
-  export BD_GIT_HOOK=1
-  _bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
-  if command -v timeout >/dev/null 2>&1; then
-    timeout "$_bd_timeout" bd hooks run pre-commit "$@"
-    _bd_exit=$?
-    if [ $_bd_exit -eq 124 ]; then
-      echo >&2 "beads: hook 'pre-commit' timed out after ${_bd_timeout}s — continuing without beads"
-      _bd_exit=0
-    fi
-  else
-    bd hooks run pre-commit "$@"
-    _bd_exit=$?
-  fi
-  if [ $_bd_exit -eq 3 ]; then
-    echo >&2 "beads: database not initialized — skipping hook 'pre-commit'"
-    _bd_exit=0
-  fi
-  if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
-fi
-# --- END BEADS INTEGRATION v0.61.0 ---

data/.beads/hooks/pre-push

@@ -1,24 +0,0 @@
-#!/usr/bin/env sh
-# --- BEGIN BEADS INTEGRATION v0.61.0 ---
-# This section is managed by beads. Do not remove these markers.
-if command -v bd >/dev/null 2>&1; then
-  export BD_GIT_HOOK=1
-  _bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
-  if command -v timeout >/dev/null 2>&1; then
-    timeout "$_bd_timeout" bd hooks run pre-push "$@"
-    _bd_exit=$?
-    if [ $_bd_exit -eq 124 ]; then
-      echo >&2 "beads: hook 'pre-push' timed out after ${_bd_timeout}s — continuing without beads"
-      _bd_exit=0
-    fi
-  else
-    bd hooks run pre-push "$@"
-    _bd_exit=$?
-  fi
-  if [ $_bd_exit -eq 3 ]; then
-    echo >&2 "beads: database not initialized — skipping hook 'pre-push'"
-    _bd_exit=0
-  fi
-  if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
-fi
-# --- END BEADS INTEGRATION v0.61.0 ---

data/.beads/hooks/prepare-commit-msg

@@ -1,24 +0,0 @@
-#!/usr/bin/env sh
-# --- BEGIN BEADS INTEGRATION v0.61.0 ---
-# This section is managed by beads. Do not remove these markers.
-if command -v bd >/dev/null 2>&1; then
-  export BD_GIT_HOOK=1
-  _bd_timeout=${BEADS_HOOK_TIMEOUT:-30}
-  if command -v timeout >/dev/null 2>&1; then
-    timeout "$_bd_timeout" bd hooks run prepare-commit-msg "$@"
-    _bd_exit=$?
-    if [ $_bd_exit -eq 124 ]; then
-      echo >&2 "beads: hook 'prepare-commit-msg' timed out after ${_bd_timeout}s — continuing without beads"
-      _bd_exit=0
-    fi
-  else
-    bd hooks run prepare-commit-msg "$@"
-    _bd_exit=$?
-  fi
-  if [ $_bd_exit -eq 3 ]; then
-    echo >&2 "beads: database not initialized — skipping hook 'prepare-commit-msg'"
-    _bd_exit=0
-  fi
-  if [ $_bd_exit -ne 0 ]; then exit $_bd_exit; fi
-fi
-# --- END BEADS INTEGRATION v0.61.0 ---

data/.beads/metadata.json

@@ -1,7 +0,0 @@
-{
-  "database": "dolt",
-  "backend": "dolt",
-  "dolt_mode": "embedded",
-  "dolt_server_host": "127.0.0.1",
-  "project_id": "5883e5bf-a919-4ca8-b7ee-d1cb7e08dfa5"
-}

data/.kiro/specs/advanced-sql-features-implementation/design.md

@@ -1,26 +0,0 @@
-# Design Document: Advanced SQL Features Implementation
-
-## Overview
-
-Most advanced SQL features are already implemented. This focuses on verification, testing, and minor enhancements.
-
-**Status:**
-
-- JOIN USING, recursive CTEs, set operations, error handling: ✅ Implemented
-- Window functions: ✅ Basic support exists
-- DuckDB configuration: ✅ Basic PRAGMA support exists
-
-**Remaining Work:**
-
-- Test window functions with actual DuckDB
-- Test advanced expressions (arrays, JSON)
-- Add user-friendly configuration methods
-- Integration testing
-
-## Implementation Approach
-
-1. **Test existing functionality** - Verify implemented features work correctly
-2. **Add convenience methods** - User-friendly configuration interface
-3. **Integration testing** - Test with actual DuckDB databases
-
-This is primarily testing and verification, not new feature implementation.

data/.kiro/specs/advanced-sql-features-implementation/requirements.md

@@ -1,43 +0,0 @@
-# Requirements Document
-
-## Introduction
-
-Most advanced SQL features are already implemented. This focuses on remaining verification and testing needs.
-
-## Requirements
-
-### Requirement 1: Window Function Verification
-
-**User Story:** As a developer, I want to verify window functions work correctly with DuckDB.
-
-#### Acceptance Criteria
-
-1. WHEN I use window functions THEN they SHALL generate correct SQL and execute properly
-2. WHEN I use LAG/LEAD functions THEN they SHALL support offset and default parameters
-
-### Requirement 2: Advanced Expression Testing
-
-**User Story:** As a developer, I want to test advanced DuckDB expressions work correctly.
-
-#### Acceptance Criteria
-
-1. WHEN I use array syntax THEN it SHALL use DuckDB's `[1, 2, 3]` format
-2. WHEN I use JSON functions THEN they SHALL work with DuckDB's JSON support
-
-### Requirement 3: Configuration Interface Enhancement
-
-**User Story:** As a developer, I want user-friendly configuration methods.
-
-#### Acceptance Criteria
-
-1. WHEN I use `db.set_pragma(key, value)` THEN it SHALL execute PRAGMA statements
-2. WHEN I use `db.configure_duckdb(options)` THEN it SHALL apply multiple settings
-
-### Requirement 4: Integration Testing
-
-**User Story:** As a developer, I want comprehensive integration tests.
-
-#### Acceptance Criteria
-
-1. WHEN I run tests THEN all advanced features SHALL work with actual DuckDB databases
-2. WHEN errors occur THEN they SHALL be properly mapped to Sequel exceptions

data/.kiro/specs/advanced-sql-features-implementation/tasks.md

@@ -1,28 +0,0 @@
-# Implementation Plan
-
-Most advanced SQL features are already implemented. Remaining tasks based on current code analysis:
-
-- [x] 1. Test window functions
-
-  - ~~Add tests to `test/dataset_test.rb` for ROW_NUMBER, RANK, DENSE_RANK~~ ✅ Already implemented
-  - ~~Test LAG/LEAD functions with offset and default parameters~~ ✅ Already implemented
-  - _Requirements: 1.1, 1.2_
-
-- [x] 2. Test advanced expressions
-
-  - Add tests to `test/sql_test.rb` for DuckDB array syntax `[1, 2, 3]`
-  - Test JSON functions like `json_extract`
-  - _Requirements: 2.1, 2.2_
-
-- [x] 3. Add configuration convenience methods
-
-  - Add `set_pragma(key, value)` method to `DatabaseMethods` (user-friendly wrapper)
-  - Add `configure_duckdb(options)` method for batch configuration
-  - Add tests to `test/database_test.rb`
-  - _Requirements: 3.1, 3.2_
-
-- [x] 4. Integration testing
-
-  - ~~Add integration tests to existing test files using actual DuckDB databases~~ ✅ Already implemented
-  - ~~Test that all advanced features work together correctly~~ ✅ Already implemented
-  - _Requirements: 4.1, 4.2_