Repository navigation
Release v0.2.1
Release Notes - v0.2.1
π New Features
PostgreSQL Array Field Support
The BaseRepository now supports native PostgreSQL array columns with the new array_fields parameter. This allows you to preserve list fields as PostgreSQL arrays (e.g., TEXT[], INTEGER[]) instead of converting them to JSONB.
class OAuthClient(BaseModel):
id: UUID
redirect_uris: list[str] # PostgreSQL TEXT[] array
grant_types: list[str] # PostgreSQL TEXT[] array
metadata: dict[str, Any] # JSONB field
class ClientRepository(BaseRepository[OAuthClient, UUID]):
def __init__(self, db_connection):
super().__init__(
db_connection=db_connection,
table_name="oauth_clients",
model_class=OAuthClient,
primary_key="id",
auto_detect_json=True, # Detects metadata as JSON
array_fields={"redirect_uris", "grant_types"} # Keep as arrays
)Automatic Date Field Conversion
The new date_fields parameter enables automatic conversion between PostgreSQL DATE/TIMESTAMP types and ISO format strings in Pydantic models.
class User(BaseModel):
id: UUID
username: str
birthdate: str | None # Expects ISO date string
created_at: str # Expects ISO datetime string
class UserRepository(BaseRepository[User, UUID]):
def __init__(self, db_connection):
super().__init__(
db_connection=db_connection,
table_name="users",
model_class=User,
primary_key="id",
date_fields={"birthdate", "created_at"} # Auto-convert dates
)π§ Improvements
- Array fields take precedence over JSON auto-detection
- Date fields handle both date objects and strings transparently
- Better handling of mixed field types in complex models
π Bug Fixes
- Fixed psycopg adapter check to prevent array handling conflicts
- psycopg adapters now disabled by default to ensure correct array field processing
π Documentation
- Added comprehensive examples in
examples/array_and_date_fields.py - Updated
docs/jsonb_support.mdwith array and date field configuration - Added test coverage for array and date field functionality
π Breaking Changes
- psycopg JSON adapters are now disabled by default to prevent conflicts with array field handling. This ensures that PostgreSQL arrays are preserved correctly when using
array_fields.