在前后端开发联调前 的提交20260223

This commit is contained in:
Neo
2026-02-23 23:02:20 +08:00
parent 254ccb1e77
commit fafc95e64c
1142 changed files with 10366960 additions and 36957 deletions

View File

@@ -0,0 +1,100 @@
- [P20260222-183858] 2026-02-22 18:38:58 +0800
- summary: CONTEXT TRANSFER: We are continuing a conversation that had gotten too long. Here is a summary: --- ## TASK 1: Database …
- prompt:
```text
CONTEXT TRANSFER: We are continuing a conversation that had gotten too long. Here is a summary:
---
## TASK 1: Database DDL Audit and Consolidation
**STATUS**: in-progress
**USER QUERIES**: 1 ("审查任务:查库现在数据库(测试数据库test_etl_feiqiu 和 test_zqyy_app)以数据库现状为准对db目录下的各个sql文件整合输出一套最全的DDL")
**DETAILS**:
- The user wants to audit two test PostgreSQL databases (`test_etl_feiqiu` and `test_zqyy_app`), compare with existing SQL files under `db/` directory, and produce a single consolidated DDL output for production migration.
- Two MCP database connections: `mcp_pg_etl_test_*` (for test_etl_feiqiu) and `mcp_pg_app_test_*` (for test_zqyy_app).
- ALL database metadata has been SUCCESSFULLY retrieved and is available in conversation context:
**test_etl_feiqiu database - COMPLETE DATA COLLECTED:**
- `meta` schema: 3 tables (etl_cursor, etl_run, etl_task) - full CREATE TABLE DDL retrieved
- `ods` schema: 21 tables - full CREATE TABLE DDL retrieved
- `dwd` schema: 40 tables - full CREATE TABLE DDL retrieved
- `core` schema: 7 tables - full CREATE TABLE DDL retrieved
- `dws` schema: 31 tables - full CREATE TABLE DDL retrieved
- `app` schema: 0 tables (only views)
- All constraints (PK, UK, FK, CHECK) for ALL schemas retrieved
- All indexes for ALL schemas retrieved (very large set - ~150+ indexes)
- All views: 7 in app schema, 1 in dws schema (v_member_recall_priority)
- All materialized views: 8 in dws schema (mv_dws_assistant_daily_detail_l1-l4, mv_dws_finance_daily_summary_l1-l4)
- All sequences: 31 in meta+dws schemas
**test_zqyy_app database - COMPLETE DATA COLLECTED:**
- `public` schema: 12 tables - full CREATE TABLE DDL retrieved
- `test` schema: 1 table (xcx-test) - trivial test table
- All constraints retrieved
- All indexes retrieved (17 indexes)
- All sequences: 7 in public schema
**FDW setup**: Read from `db/fdw/setup_fdw.sql` - maps etl_feiqiu.app to zqyy_app.fdw_etl
**WHAT WAS STARTED BUT NOT COMPLETED:**
- A Python script `scripts/ops/gen_consolidated_ddl.py` was created but is INCOMPLETE - only the header/structure was written, the script was cut off mid-write. The file contains the framework (section functions, output path logic) but the actual DDL data constants (META_TABLES, ODS_TABLES, DWD_TABLES, etc.) are empty/missing. The file ends with `META_TABLES = """\` - an unclosed string.
**NEXT STEPS**:
The new agent has TWO viable approaches:
**Approach A (Recommended): Write the DDL file directly** instead of via Python script:
1. Delete or ignore the incomplete `scripts/ops/gen_consolidated_ddl.py`
2. Write `docs/database/consolidated_ddl.sql` directly using fsWrite/fsAppend
3. Organize by: database → schema → sequences → tables → constraints (PK/UK/FK only, skip NOT NULL) → indexes → views → materialized views → FDW
4. Re-query the databases using MCP tools to get the DDL content (the previous query results are in conversation history but may be truncated in transfer)
**Approach B: Fix the Python script** and run it - but this requires embedding all DDL as string constants which is unwieldy.
**Key data to re-query from databases** (if previous results are lost in context transfer):
- For each schema: `CREATE TABLE` DDL via information_schema.columns join
- Constraints: `pg_get_constraintdef()` - filter to only PK, UK, FK (skip NOT NULL as they're inline)
- Indexes: `pg_get_indexdef()` where NOT indisprimary AND NOT indisunique
- Views: `pg_views.definition`
- Materialized views: `pg_matviews.definition`
- Sequences: `information_schema.sequences`
**FILEPATHS**:
- `scripts/ops/gen_consolidated_ddl.py` (INCOMPLETE - created but cut off mid-write)
- `docs/database/consolidated_ddl.sql` (TARGET OUTPUT - not yet created)
- `db/fdw/setup_fdw.sql` (reference - already read)
- `db/README.md` (reference - already read)
**USER CORRECTIONS AND INSTRUCTIONS**:
- 以数据库现状为准 (database reality takes precedence over SQL files)
- Output should be a single complete DDL set for production migration reference
- Language: Chinese preferred for documentation/comments
- MCP tools: `mcp_pg_etl_test_execute_sql` (for test_etl_feiqiu) and `mcp_pg_app_test_execute_sql` (for test_zqyy_app)
- The `app` schema in etl_feiqiu has NO tables, only views (confirmed by empty query result)
- NOT NULL constraints should be inline in CREATE TABLE, not listed separately as ALTER TABLE
- Steering rules require: db-docs.md compliance (变更说明, 兼容性, 回滚策略, 验证步骤)
Files to read:
- `scripts/ops/gen_consolidated_ddl.py`
- `db/fdw/setup_fdw.sql`
- `db/README.md`
USER QUERIES(most recent first):
1. Output:
Command executed successfully with no output.
Exit Code: 0
2. Output:
Command executed successfully with no output.
Exit Code: 0
---
METADATA:
The previous conversation had 2 messages.
INSTRUCTIONS:
Continue working until the user query has been fully addressed. Do not ask for clarification - proceed with the work based on the context provided.
IMPORTANT: you need to read from the files to Read section
```