rhosocial-activerecord-mysql 1.0.0.dev9

MySQL backend implementation for rhosocial-activerecord, providing a robust and optimized MySQL database support.

rhosocial-activerecord-mysql ($\rho_{\mathbf{AR}\text{-mysql}}$)

MySQL Backend for rhosocial-activerecord

Production-Ready MySQL Support · Sync & Async · Native Driver Integration

Note: This is a backend implementation for rhosocial-activerecord. It cannot be used standalone.

Why This Backend?

1. MySQL-Specific Optimizations

Feature	This Backend	Generic Solutions
Full-Text Search	Native MATCH ... AGAINST	LIKE-based workarounds
JSON Operations	JSON_EXTRACT, ->>, ->	Serialize/deserialize overhead
Upsert	ON DUPLICATE KEY UPDATE	Manual check-then-insert
Connection Pooling	Built-in with mysql-connector	External pooling required

2. True Sync-Async Parity

Same API surface for both sync and async operations:

# Sync
users = User.query().where(User.c.age >= 18).all()

# Async - just add await
users = await User.query().where(User.c.age >= 18).all()

3. Built for Production

• Connection pooling with configurable pool sizes
• Transaction support with proper isolation levels
• Error mapping from MySQL error codes to Python exceptions
• Type adapters for MySQL-specific data types

Quick Start

Installation

pip install rhosocial-activerecord-mysql

Basic Usage

from rhosocial.activerecord.model import ActiveRecord
from rhosocial.activerecord.backend.impl.mysql import MySQLBackend
from rhosocial.activerecord.backend.impl.mysql.config import MySQLConnectionConfig
from typing import Optional

class User(ActiveRecord):
    __table_name__ = "users"
    id: Optional[int] = None
    name: str
    email: str

# Configure
config = MySQLConnectionConfig(
    host="localhost",
    port=3306,
    database="myapp",
    username="user",
    password="password"
)
User.configure(config, MySQLBackend)

# Use
user = User(name="Alice", email="[e-mail]")
user.save()

# Query with MySQL full-text search
results = User.query().where(
    "MATCH(name, email) AGAINST(? IN BOOLEAN MODE)",
    ("+Alice",)
).all()

💡 AI Prompt: "Show me how to use JSON operations in MySQL with this backend"

MySQL-Specific Features

Full-Text Search

Native MySQL full-text search support:

# Boolean mode full-text search
Article.query().where(
    "MATCH(title, content) AGAINST(? IN BOOLEAN MODE)",
    ("+python -java",)
).all()

# Natural language mode
Article.query().where(
    "MATCH(title, content) AGAINST(?)",
    ("database optimization",)
).all()

JSON Operations

Query JSON columns using MySQL's native JSON functions:

# Extract JSON value
User.query().where("settings->>'$.theme' = ?", ("dark",)).all()

# JSON contains
Product.query().where("JSON_CONTAINS(tags, ?)", ('"featured"',)).all()

Upsert (ON DUPLICATE KEY UPDATE)

Efficient insert-or-update operations:

# Will update on duplicate key
User.insert_or_update(
    name="Alice",
    email="[e-mail]",
    update_fields=["name"]  # Only update name on conflict
)

Requirements

• Python: 3.8+ (including 3.13t/3.14t free-threaded builds)
• Core: rhosocial-activerecord>=1.0.0
• Driver: mysql-connector-python>=9.0.0

Get Started with AI Code Agents

This project supports AI-assisted development. Clone and open in your preferred tool:

git clone https://github.com/rhosocial/python-activerecord-mysql.git
cd python-activerecord-mysql

Example AI Prompts

• "How do I configure connection pooling for MySQL?"
• "Show me the differences between MySQL and PostgreSQL backends"
• "How do I use MySQL-specific JSON operators?"
• "Create a model with a FULLTEXT index"

For Any LLM

Feed the documentation files in docs/ to your preferred LLM for context-aware assistance.

Testing

⚠️ CRITICAL: Tests MUST run serially. Do NOT use pytest -n auto or parallel execution.

# Run all tests
PYTHONPATH=src pytest tests/

# Run specific feature tests
PYTHONPATH=src pytest tests/rhosocial/activerecord_mysql_test/feature/basic/
PYTHONPATH=src pytest tests/rhosocial/activerecord_mysql_test/feature/query/

See the Testing Documentation for details.

Documentation

• Getting Started — Installation and configuration
• MySQL Features — MySQL-specific capabilities
• Type Adapters — Data type handling
• Transaction Support — Transaction management

Comparison with Other Backends

Feature	MySQL	PostgreSQL	SQLite
Full-Text Search	✅ Native	✅ Native	⚠️ FTS5 extension
JSON Type	✅ JSON	✅ JSONB	⚠️ JSON1 extension
Arrays	❌	✅ Native	❌
Upsert	✅ ON DUPLICATE KEY	✅ ON CONFLICT	✅ ON CONFLICT
Returning	❌	✅ RETURNING	✅ RETURNING

💡 AI Prompt: "When should I choose MySQL over PostgreSQL for my project?"

Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

License

Apache License 2.0 — Copyright © 2026 vistart

---

Built with ❤️ by the rhosocial team

GitHub · Documentation · PyPI