-
Notifications
You must be signed in to change notification settings - Fork 52
1.x #701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* SRID fix for mariadb/mysql * Axis order updates for mysql
Spatial axis order , srid migrations
get document fix
|
Caution Review failedThe pull request is closed. WalkthroughIntroduces axis-order capability queries and centralized spatial geometry construction across adapters. Adds Database::EARTH_RADIUS. Refactors spatial SQL generation (distance, predicates, projections, and type definitions) to use getSpatialGeomFromText and new getSpatialSQLType. Enhances Spatial validator with coordinate-range checks and expands tests, including invalid coordinates and polygon nesting. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Client
participant Adapter as SQL Adapter
participant Impl as Concrete Adapter (MySQL/MariaDB/Postgres/SQLite)
participant DB as Database
Client->>Adapter: Create/Query with spatial attributes (WKT)
Adapter->>Impl: getSupportForSpatialAxisOrder()
Impl-->>Adapter: true/false
note over Adapter: Build SQL using getSpatialGeomFromText(<wkt>, <srid>)<br/>Append axis-order spec only if supported
alt Distance in meters
Adapter->>DB: ST_Distance(..., getSpatialGeomFromText(...), 'metre') / geography cast
else Distance non-meters
Adapter->>DB: ST_Distance(..., getSpatialGeomFromText(...))
end
Adapter-->>Client: Results (spatial projections via ST_AsText[+axis-order?])
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested reviewersPoem
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (11)
✨ Finishing touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary by CodeRabbit