oxibase 0.3.2

Autonomous relational database management system with MVCC, time-travel queries, and full ACID compliance
Documentation
---
layout: default
title: Connection String Reference
parent: Getting Started
nav_order: 3
---

# Connection String Reference

This document provides information about Oxibase connection string formats and their usage.

## Connection String Basics

Oxibase connection strings follow a URL-like format:

```
scheme://[path][?options]
```

Where:
- `scheme` specifies the storage mode (memory or file)
- `path` provides location information for persistent storage
- `options` are optional query parameters for configuration

## Storage Modes

Oxibase supports two storage modes:

### In-Memory Mode (memory://)

```
memory://
```

All data stored in RAM:
- Maximum performance for temporary data
- Full MVCC transaction isolation
- Data is lost when the process terminates
- Ideal for testing and ephemeral workloads

### Persistent Mode (file://)

```
file:///path/to/data
```

Data persisted to disk:
- WAL (Write-Ahead Logging) for crash recovery
- Periodic snapshots for fast recovery
- Same MVCC features as memory mode
- Survives process restarts

Examples:
```
file:///data/mydb
file:///Users/username/oxibase/data
file:///tmp/test_db
```

## Configuration Options

Configuration can be set via query parameters in the connection string:

```
file:///path/to/data?sync_mode=normal&snapshot_interval=60
```

| Option | Values | Default | Description |
|--------|--------|---------|-------------|
| `sync_mode` | none, normal, full (or 0, 1, 2) | normal | WAL synchronization mode |
| `snapshot_interval` | Integer (seconds) | 300 | Time between automatic snapshots |
| `keep_snapshots` | Integer | 3 | Number of snapshots to retain |
| `wal_flush_trigger` | Integer | 1000 | Operations before WAL flush |

### Sync Mode Details

| Mode | Value | Description |
|------|-------|-------------|
| none | 0 | No sync (fastest, risk of data loss) |
| normal | 1 | Sync on flush (balanced) |
| full | 2 | Sync every write (maximum durability) |

## Usage Examples

### Rust API

```rust
use oxibase::Database;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    // In-memory database
    let db = Database::open("memory://")?;

    // Or create a unique in-memory instance
    let db = Database::open_in_memory()?;

    // Persistent database
    let db = Database::open("file:///data/mydb")?;

    // With configuration options
    let db = Database::open("file:///data/mydb?sync_mode=full&snapshot_interval=60")?;

    // Execute SQL
    db.execute("CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)", ())?;
    db.execute("INSERT INTO users VALUES ($1, $2)", (1, "Alice"))?;

    // Query data
    for row in db.query("SELECT * FROM users WHERE id = $1", (1,))? {
        let row = row?;
        let name: String = row.get("name")?;
        println!("Name: {}", name);
    }

    Ok(())
}
```

### Command Line

```bash
# In-memory database (default)
oxibase

# Persistent database
oxibase --db "file:///data/mydb"

# With configuration
oxibase --db "file:///data/mydb?sync_mode=full"

# Execute a query directly
oxibase --db "file:///data/mydb" -q "SELECT * FROM users"
```

## PRAGMA Configuration

You can also configure settings after connection using PRAGMA commands:

```sql
-- Set configuration values
PRAGMA sync_mode = 2;
PRAGMA snapshot_interval = 60;
PRAGMA keep_snapshots = 5;
PRAGMA wal_flush_trigger = 500;

-- Read current values
PRAGMA sync_mode;
PRAGMA snapshot_interval;

-- Create a snapshot manually
PRAGMA create_snapshot;
```

See the [PRAGMA Commands](pragma-commands) documentation for details.

## Best Practices

1. **Development**: Use `memory://` for fast iteration and testing
2. **Production**: Use `file://` with appropriate `sync_mode`
3. **Critical data**: Set `sync_mode=full` for maximum durability
4. **High throughput**: Use `sync_mode=normal` with periodic `PRAGMA create_snapshot`
5. **Limited disk space**: Reduce `keep_snapshots` to retain fewer snapshots