Skip to content

docs: revert PostGIS/geometry fields documentation#7909

Merged
ankur-arch merged 2 commits into
mainfrom
DR-8591-ankur
May 20, 2026
Merged

docs: revert PostGIS/geometry fields documentation#7909
ankur-arch merged 2 commits into
mainfrom
DR-8591-ankur

Conversation

@ankur-arch
Copy link
Copy Markdown
Contributor

@ankur-arch ankur-arch commented May 20, 2026

Why: PostGIS support is not currently available in Prisma ORM, so the documentation was removed to avoid misleading users.

Summary by CodeRabbit

  • Documentation
    • Fixed code block formatting in CRUD documentation
    • Removed geometry fields documentation
    • Removed PostGIS extension documentation
    • Updated PostgreSQL extensions documentation with clarified limitations on custom types

Review Change Stack

Why: PostGIS support is not currently available in Prisma ORM, so the
documentation was removed to avoid misleading users.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blog Ready Ready Preview, Comment May 20, 2026 1:18pm
docs Ready Ready Preview, Comment May 20, 2026 1:18pm
eclipse Ready Ready Preview, Comment May 20, 2026 1:18pm
site Ready Ready Preview, Comment May 20, 2026 1:18pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 20, 2026

🍈 Lychee Link Check Report

72 links: ✅ 47 OK | 🚫 0 errors | 🔀 1 redirects | 👻 24 excluded

✅ All links are working!


Full Statistics Table
Status Count
✅ Successful 47
🔀 Redirected 1
👻 Excluded 24
🚫 Errors 0
⛔ Unsupported 0
⏳ Timeouts 0
❓ Unknown 0

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1098e72f-1d44-451e-bd73-13a16598241c

📥 Commits

Reviewing files that changed from the base of the PR and between 2489dc7 and 4139f66.

📒 Files selected for processing (4)
  • apps/docs/content/docs/orm/prisma-client/queries/crud.mdx
  • apps/docs/content/docs/orm/prisma-client/special-fields-and-types/working-with-geometry-fields.mdx
  • apps/docs/content/docs/orm/prisma-schema/postgresql-extensions.mdx
  • apps/docs/content/docs/postgres/database/postgres-extensions.mdx
💤 Files with no reviewable changes (3)
  • apps/docs/content/docs/orm/prisma-client/special-fields-and-types/working-with-geometry-fields.mdx
  • apps/docs/content/docs/postgres/database/postgres-extensions.mdx
  • apps/docs/content/docs/orm/prisma-schema/postgresql-extensions.mdx

Walkthrough

This PR consolidates PostGIS geometry documentation by removing dedicated files, simplifying extension guides, and clarifying current limitations for Prisma's extension type support. A minor CRUD documentation formatting issue is also corrected.

Changes

Documentation updates

Layer / File(s) Summary
CRUD example code fence correction
apps/docs/content/docs/orm/prisma-client/queries/crud.mdx
Code fence terminates properly in the "Filter by related records" section, allowing the "Filtering and sorting" reference link to appear after the complete code block rather than interrupting it.
PostGIS documentation consolidation and extension limitations
apps/docs/content/docs/orm/prisma-client/special-fields-and-types/working-with-geometry-fields.mdx, apps/docs/content/docs/orm/prisma-schema/postgresql-extensions.mdx, apps/docs/content/docs/postgres/database/postgres-extensions.mdx
Removed working-with-geometry-fields.mdx file (984 lines), deleted the entire "PostGIS extension for spatial data" section from the Prisma schema extension guide, and updated the Limitations section to clarify that Prisma Studio cannot deserialize custom extension types (e.g., VECTOR) and Prisma ORM represents unimplemented extension types as Unsupported, requiring raw SQL for queries. The outdated "PostGIS is coming in 2026" claim is removed.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: revert PostGIS/geometry fields documentation' directly and accurately summarizes the main change—removal of PostGIS/geometry documentation to align with current product capabilities.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


Comment @coderabbitai help to get the list of available commands and usage tips.

@argos-ci
Copy link
Copy Markdown

argos-ci Bot commented May 20, 2026

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ✅ No changes detected - May 20, 2026, 1:25 PM

@ankur-arch ankur-arch merged commit b104092 into main May 20, 2026
19 checks passed
@ankur-arch ankur-arch deleted the DR-8591-ankur branch May 20, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants