Show exact database relations and bound ClickHouse context - #28
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Проблема
Database Schema показывал только общую ORM-связь без точной пары полей, а несколько внешних ключей к одной таблице сливались. ClickHouse при клике на сервис открывал глобальную сцену с тысячами структур, долго строился и визуально схлопывался в одну линию.
Что изменено
sourceColumns → targetColumnsALTER TABLE ... FOREIGN KEYтеперь разбирается вместе с constraint,ON DELETEиON UPDATElink_logs.linkId → links.idПроверка
pl-api: 10 714 nodes / 27 445 edgeslink_logs: 4 точных FK, включая две разные связи сusers.idAnalyticsClickhouseServiceone-hop context: около 4 ms, 15 nodes / 14 edgesЛокальные проверки, которым нужен запуск дочернего HTTP/CLI процесса, ограничены sandbox Codex; GitHub Actions запускает их на обычных runners.