Download the PHP package semhoun/neuron-paradedb without Composer

ParadeDB for Neuron AI

English | Français

Vector similarity and BM25 hybrid search in PostgreSQL for PHP RAG applications using Neuron AI.

Overview

semhoun/neuron-paradedb connects Neuron AI to ParadeDB through PDO. It combines cosine-distance semantic search and BM25 lexical search using Reciprocal Rank Fusion (RRF). Documents, embeddings and metadata share one table, without a separate search service or PHP ParadeDB client.

Collections separate documents within that table. Neuron AI's typed filters apply to searches and deletions.

Technologies and Compatibility

Since version 3.0.0, the package's major version follows Neuron AI's major version. Minor and patch versions remain independent.

The examples below target Neuron AI 4. Package 4.x does not support Neuron AI 3.

Architecture

HybridRetrieval embeds a message's text, combines mandatory filters with AND, then calls the hybrid store. ParadeDBVectorStore validates documents and delegates filter compilation to ParadeDBFilterCompiler before executing PDO queries.

• The HNSW index uses cosine distance; the BM25 index covers content and the technical key search_id.
• Each hybrid branch selects at most 2 * topK candidates, then RRF keeps the best topK results.
• Collections and filters apply before ranking and limits in both branches.
• HybridVectorStoreInterface extends Neuron's interface with hybridSearch(string $query, array $embedding, ?FilterExpression $filters = null, ?int $topK = null): iterable.
• HybridRetrieval::retrieve() materializes results into an array, including results from custom lazy stores.

Installation

Prerequisites

• PHP 8.1 or newer in the 8.x series, with the extensions listed above.
• Composer 2, as used in CI.
• A ParadeDB server with vector and pg_search installed; PostgreSQL with pgvector alone is insufficient.
• An embeddings provider for ingestion and queries; the examples use OpenAI, but it is not required.
• Docker with Compose for local integration tests only.

From your consuming application:

Configuration

The library receives a PDO connection and does not load .env files. Supply these variables to the PHP process to use the examples:

Initialize the Store

Run provisioning explicitly with an administrative role, not on every application request:

The constructor enables PDO exceptions and checks an existing table for compatibility without creating objects. setupDatabase() creates missing extensions, the table and indexes; it is not a migration tool. An incompatible embedding dimension is rejected.

Table names must be single ASCII identifiers of at most 48 characters, without schema qualification. Letters and underscores are allowed initially, followed by letters, underscores or digits. Use a trusted, fixed search_path.

Ingest and Search

The following blocks reuse the store initialized above. Use embeddings with the same dimension and model for ingestion and retrieval.

For an existing agent extending NeuronAI\RAG\RAG, with its AI provider already configured:

This repository has no application server or startup command: these components run within your PHP application.

Collections and Filters

forCollection() returns a clone sharing PDO, the schema and options, without executing SQL or mutating the original. Pass the same collection-scoped store to the agent and its retrieval strategy.

• null selects only documents without a collection, never all collections.
• Collection IDs are nonempty strings without normalization; '' is reserved in SQL for the uncollected scope.
• The primary key (collection_id, id) allows the same document ID across collections. search_id remains a globally unique internal BM25 key.
• Metadata keys ragId and collection_id never change the scope. There is no all-collections search or deletion mode.
• This application-level separation is neither authorization nor PostgreSQL RLS. BM25 statistics remain shared across the table.
• dropTable() deletes the entire table and its indexes, even from a collection clone.

Declare filterable metadata in a schema. Native fields sourceType and sourceName are also available:

The optional schema defaults to DocumentSchema::default(). Metadata remains stored as JSON; only declared filterable fields and native fields can be filtered. Use Document getters/setters, not public properties.

Operators: eq, neq, in, numeric gt/gte/lt/lte, containsAny/containsAll for string arrays, and FilterGroup::allOf/anyOf groups. neq requires a required field. Null comparisons, undeclared fields, incompatible values and raw filters are rejected before execution.

Values and metadata keys are bound parameters; JSONB preserves scalar types. The collection constraint, strategy filters and per-call filters are combined with AND. An OR group cannot widen those scopes. Calls do not mutate store defaults.

The schema validates new documents but does not migrate or revalidate historical metadata. Audit existing data before adding a required field or changing its type.

Writes and Scores

• addDocument() and addDocuments() require precomputed embeddings. An existing ID within the collection produces an upsert preserving search_id.
• Batches are validated before writing and processed atomically. An existing transaction uses a savepoint without committing the caller's work. Empty batches are no-ops; this is not a PostgreSQL COPY loader.
• Vectors must be finite, nonzero and of the exact dimension, with a finite, nonzero float32 squared norm. Unsafe magnitudes are rejected without normalization. HNSW vector indexes support up to 2,000 dimensions.
• Results contain a string ID, content, embedding, sources, metadata and score. Vector scores use Neuron's cosine conversion; hybrid scores sum 1 / (rrfK + rank) per branch and are not probabilities.
• dimensions, topK and rrfK must be positive. A larger rrfK reduces the relative weight of top-ranked positions. HNSW remains approximate.
• Legacy helpers similaritySearch($embedding), deleteBy($type, $name) and deleteBy(array) remain adapter-specific. The array must contain nonempty source constraints with string values, combined with AND. deleteBySource() is deprecated; no Neuron 3 compatibility layer is loaded.

Provisioning and Migration

Production Permissions

setupDatabase() runs CREATE EXTENSION IF NOT EXISTS for vector and pg_search, then creates the table and indexes. Use a provisioning role permitted to create those extensions, create objects in the schema and manage the table's indexes. The extensions must be installed on the server.

After provisioning, a separate, existing application role, named neuron_app here, needs only:

Integration tests verify writes, searches and deletions without identity-sequence privileges on the pinned ParadeDB image. This applies to GENERATED ALWAYS AS IDENTITY, not arbitrary sequences or SERIAL. Do not call setupDatabase() with the restricted role; permission errors are propagated.

The repository provides no application deployment or production compilation step. compose.yaml is for testing only. Keep PostgreSQL credentials out of source code.

Legacy 1.0 Tables

The schema introduced in 1.1 is required, even without named collections. The constructor and setupDatabase() reject legacy tables without migrating them. Run this static method before constructing the store, using a table-owner connection and the existing dimension:

The migration adds collection_id TEXT NOT NULL DEFAULT '', replaces the primary key with (collection_id, id), adds a unique search_id BIGINT GENERATED ALWAYS AS IDENTITY and rebuilds BM25 on (search_id, content). Documents, metadata and the HNSW index are preserved; existing documents belong to the null scope.

The operation is transactional with an exclusive lock, or uses a savepoint within an existing transaction. Locks can then last until that transaction ends. Errors roll back changes; external dependencies are never removed with CASCADE. An already migrated table remains unchanged except for a missing BM25 index being created. Missing or partially migrated tables are rejected.

Back up the database, test migration and rollback on a copy, then schedule maintenance without application access. Do not mix versions 1.0 and 1.1 against the same table or run this migration on every request. New installations use setupDatabase() directly.

Moving from package 3.x to 4.x requires updating Neuron and Document access, but no new physical migration.

Development and Testing

The three unit test files cover validation, filter compilation and hybrid retrieval without a database or API key. The integration test file covers schema, scores, collections, filters, upserts, transactions/savepoints, migrations and restricted permissions.

For local integration tests, use only a disposable database with administrative privileges. Compose exposes it on localhost. Export PARADEDB_USER and PARADEDB_PASSWORD using the test values defined in compose.yaml, then run:

Tests create and remove temporary tables and a restricted role. Without PARADEDB_DSN, they are skipped. The final command removes the containers and associated volumes.

CI configures PHP 8.1 through 8.5, including a PHP 8.1 job with lowest dependencies. Integration uses PHP 8.3 and paradedb/paradedb:0.25.9-pg18. Previously recorded local validation used PHP 8.5.10, Neuron AI 4.0.0, PostgreSQL 18.6 and pgvector 0.8.4. Later ParadeDB versions are not yet qualified.

Contributing

1. Fork the repository and create a dedicated branch.
2. Add relevant tests in tests/Unit or tests/Integration.
3. Run the validation commands above, and integration tests for SQL changes.
4. Use composer style to apply formatting, then open a pull request describing the change.

License

MIT. Copyright 2026 Nathanael (semhoun).