[sync] chore: add performace trace trigger T4666#3223
Conversation
Synced from teableio/teable-ee@86f5cdc 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-Teable <jocky@teable.ai> Co-authored-by: Jun Lu <hammond@teable.io> Co-authored-by: Pengap <penganpingprivte@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: 91a440ef4d
ℹ️ 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".
| for (const key of metaDatabaseEnvKeys) { | ||
| const value = env[key]; | ||
| if (value) { | ||
| return value; |
There was a problem hiding this comment.
Restore
PRISMA_DATA_DATABASE_URL lookup for data target
getDatabaseUrl now iterates only metaDatabaseEnvKeys even when target === 'data', so environments that still split meta/data databases will route all data-plane Prisma clients to the meta database and ignore PRISMA_DATA_DATABASE_URL. In those deployments, data queries will hit the wrong DB (typically missing data-plane tables), causing runtime failures and effectively breaking dual-DB setups that previously worked.
Useful? React with 👍 / 👎.
🧹 Preview Environment Cleanup
|
🔄 Automated sync from EE repository.
53 commit(s) synced since last sync.
Authors
Included commits
Latest source commit: teableio/teable-ee@86f5cdc
This PR was automatically created by the sync workflow.