Skip to content

docs: distinguish experimental ORM adapters from validated CUBRID-native packages #89

Open

Description

@yeongseon

Problem — organization profile accuracy (2026-11-12)

The public profile/README.md lists drizzle-cubrid as a "Drizzle ORM dialect with type-safe schema" (beta) and sea-orm-cubrid as "SeaORM backend for CUBRID" (alpha), alongside recommendations to use each. These status badges accurately signal immaturity, but do not disclose the verified implementation boundary: both currently generate SQL via MySQL-specific ORM implementations, and their CUBRID-native compiler/real-server compatibility work remains incomplete.

Required bounded correction

  • Keep beta/alpha/in-progress, but describe the current MySQL-backed prototype explicitly, not as a completed CUBRID-native dialect. Note that a CUBRID connection/proxy does not imply a native SQL compiler.
  • Clearly distinguish the production/public readiness of the existing Python CUBRID-only driver/SQLAlchemy dialect from experimental Drizzle/SeaORM adapters. Avoid giving a stable recommendation for adapters without a verified native compiler and non-vacuous CUBRID test evidence.
  • The profile currently refers to cookbook templates as "production-ready Python examples"; cross-check against current SQLite fallback tests and live verification before making broad deployment claims. Do not equate a skipped/offline SQLite run with CUBRID compatibility.
  • Reference the owning repository's README/issues for current limitations instead of creating an organization-wide engineering policy. Review translations or other organization marketing copy as applicable.
  • Do not claim other-DB runtime dependencies exist in this .github repository itself. Its issue is representation of downstream release maturity.

No implementation or testing claims are changed by a docs edit. Suggested priority medium / size S after triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions