[sync] T5610 Copy legacy BYODB auto number sequences#3494
Conversation
Synced from teableio/teable-ee@d2ccd41 Co-authored-by: Aries X <caoxing9@gmail.com> Co-authored-by: Bieber <artist@teable.io> Co-authored-by: Boris <boris2code@outlook.com> Co-authored-by: Jocky Zhou <jocky@teable.ai> Co-authored-by: Jun Lu <hammond@teable.io> Co-authored-by: Pengap <penganpingprivte@gmail.com> Co-authored-by: SkyHuang <sky.huang.fe@gmail.com> Co-authored-by: Uno <uno@teable.ai> Co-authored-by: nichenqin <nichenqin@hotmail.com>
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dfdd58df64
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `IMPORT FOREIGN SCHEMA ${quoteIdent(input.sourceSchema)} LIMIT TO (${importLimit}) FROM SERVER ${quoteIdent( | ||
| input.serverName | ||
| )} INTO ${quoteIdent(input.fdwSchema)}`, |
There was a problem hiding this comment.
Import FDW dependencies for seed copy
When shared rows are copied with the postgres_fdw strategy, the computed_update_outbox_seed plan's WHERE clause references fdwSchema.computed_update_outbox, but this IMPORT FOREIGN SCHEMA ... LIMIT TO imports only the current table. The generated INSERT for that seed table will therefore fail with a missing computed_update_outbox foreign table and stop FDW-based migrations; import the dependent outbox table for this plan or avoid the cross-table predicate.
Useful? React with 👍 / 👎.
🧹 Preview Environment Cleanup
|
🔄 Automated sync from EE repository.
257 commit(s) synced since last sync.
Authors
Included commits
ai-agent-engineT5222 T3933 (Pengap)Latest source commit: teableio/teable-ee@d2ccd41
This PR was automatically created by the sync workflow.