Skip to content

Document cross_database module (renamed from migrate in 3.11)#1634

Open
imilinovic wants to merge 1 commit into
release/3.11from
cross-database
Open

Document cross_database module (renamed from migrate in 3.11)#1634
imilinovic wants to merge 1 commit into
release/3.11from
cross-database

Conversation

@imilinovic
Copy link
Copy Markdown
Contributor

@imilinovic imilinovic commented May 18, 2026

Add the cross_database reference page covering all procedures (bolt, neo4j, mysql, postgresql, sql_server, oracle_db, s3, arrow_flight, duckdb, servicenow), the Bolt type conversion rules (including the lossy 30-days-per-month Duration flattening), and the same-parameters guard.

Keep the migrate page in place with a callout pointing at the new location, since migrate.* names remain as aliases.

Release note

Please briefly explain the changes you made which will be added to the changelog.

Related product PRs

PRs from product repo this doc page is related to:
(paste the links to the PRs)
PR3832

Checklist:

  • Add appropriate milestone (current release cycle)
  • Add bugfix or feature label, based on the product PR type you're documenting
  • Make sure all relevant tech details are documented
  • Check all content with Grammarly
  • Perform a self-review of my code
  • The build passes locally
  • My changes generate no new warnings or errors

@imilinovic imilinovic added this to the 3.11 milestone May 18, 2026
@imilinovic imilinovic self-assigned this May 18, 2026
@imilinovic imilinovic added the feature Documentation related to a new product feature of feature update label May 18, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 18, 2026

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

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview, Comment May 18, 2026 1:07pm

Request Review

Add the cross_database reference page covering all procedures
(bolt, neo4j, mysql, postgresql, sql_server, oracle_db, s3,
arrow_flight, duckdb, servicenow), the Bolt type conversion rules
(including the lossy 30-days-per-month Duration flattening), the
same-parameters guard, and the migrate.* alias table.

Reduce the migrate page to a redirect stub pointing at cross_database;
the migrate.* names continue to work via Memgraph's callable-mapping
aliases, but the canonical reference now lives at cross_database.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Documentation related to a new product feature of feature update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant