【问题标题】:Optimal dot / GraphViz layout for graph DB schema图 DB 模式的最佳点/GraphViz 布局
【发布时间】:2023-03-20 09:48:01
【问题描述】:

我第一次使用 dot + GraphViz 来帮助规划图形数据库架构。

随着我添加更多节点,输出看起来不太理想。尤其是语言和国家/地区看起来相当混乱。

我尝试了一些基本的排名,但无法对其产生太大影响。

如何获得更清晰的输出?

代码:

digraph ReferenceGraph {
  nodesep = 2;
  edge [color=gray50, fontname=Calibri, fontsize=11]
  node [shape=record, fontname=Calibri, fontsize=11]

  root [label="Reference Node", color=darkgreen, fontcolor=darkgreen, fontname=Calibri, fontsize=11]

  sue [label="{{User}|{GivenName=Sue}|{FamilyName=Williams}|{Username=swilliams}|{EmailAddress=Sue.Williams@foo.com}|{BusinessPhone=02 1234 5678}|{MobilePhone=0414 123 456}|{PasswordSalt=fcd376dc}|{PasswordHash=a8635cfd2930ebc0cc78}|{PreviousPasswordSalt=gggf6dc}|{PreviousPasswordHash=wer435cfd2930ebc0cc78}|{RequirePasswordChangeOnNextLogin=true}|FailedLoginAttempts=0|LastLoginAttemptUtc=21 Jun 2011 16:43:01 UTC|{DateCreatedUtc=20 Jun 2011 15:43:07 UTC}}", color=blue, fontcolor=blue]
  sue -> root [label="ADMINISTERS"]

  clint [label="{{Client}|{UniqueId=100}|{GivenName=Clint}|{MiddleNames=ian bill}|{FamilyName=Wood}|{PreferredName=Woods}|{Gender=Male Female Unknown}|{PlaceOfBirthTown}|{PlaceOfBirthState}|{PlaceOfBirthCountry}|{Email=clint.wood@foo.com}|{LanguageComments}|{InterpreterRequired=true false}|{InterpreterComments}|{Religion=Buddhist}|{LegalOrders=order1}|{DateOfBirth=21 June 1979}|{DateOfBirthCertainty=Confirmed Unconfirmed Estimated}}", color=blue, fontcolor=blue]
  clint -> acme [label="CLIENT_BELONGS_TO"]
  clint -> english [label ="SPEAKS"]

  cat [label="Cat (Client)"]
  cat -> acme [label="CLIENT_BELONGS_TO"]
  cat -> english [label ="SPEAKS"]
  cat -> mandarin [label ="SPEAKS"]

  acme [label="{{Agency}|{UniqueId=100}|{Key=acme}|{Name=Acme Australia}}", color=blue, fontcolor=blue]
  root -> acme [label="HOSTS"]

  john [label="John (User)"]
  john -> acme [label="USER_BELONGS_TO"]

  jack [label="Jack (User)"]
  jack -> acme [label="USER_BELONGS_TO"]

  centreA [label="{{Centre}|{Name=CentreA}|{BusinessPhone=02 1234 5678}|{Fax=0414 123 456}|{Email=xyz@bcb.com}|{Status=Active}}", color=blue, fontcolor=blue]
  centreA -> acme [label="CENTRE_BELONGS_TO"]

  centreAStreetAddress [label="{{PhysicalAddress}|{Line 1=Level 1}|{Line 2=11 Sydney Road}|{TownSuburb=Sydney}|{State=NSW}|{Postcode=2000}|{Country=Australia}}", color=blue, fontcolor=blue]
  centreA -> centreAStreetAddress [label="HAS_STREET_ADDRESS"]

  centreAPostalAddress [label="PO Box 123 (PhysicalAddress)"]
  centreA -> centreAPostalAddress [label="HAS_POSTAL_ADDRESS"]

  clintCurrentAddress [label="{{CurrentAddress}|{Line 1=Level 1}|{Line 2=11 Sydney Road}|{TownSuburb=Sydney}|{State=NSW}|{Postcode=2000}|{Country=Australia}}", color=blue, fontcolor=blue]
  clint -> clintCurrentAddress [label="HAS_STREET_ADDRESS"]

  referenceData [label="Reference Data"]
  root -> referenceData [label="HAS_REFERENCE_DATA"]

  languagesReferenceData [label="Languages"]
  referenceData -> languagesReferenceData [label="HAS_LANGUAGES"]

  english [label="{{Language}|{Name=English}}", color=blue, fontcolor=blue]
  languagesReferenceData -> english [label="HAS_LANGUAGE"]

  mandarin [label="Mandarin (Language)"]
  languagesReferenceData -> mandarin [label="HAS_LANGUAGE"]

  japanese [label="Japanese (Language)"]
  languagesReferenceData -> japanese [label="HAS_LANGUAGE"]

  countriesReferenceData [label="Countries"]
  referenceData -> countriesReferenceData [label="HAS_COUNTRIES"]

  australia [label="{{Country}|{Name=Australia}}", color=blue, fontcolor=blue]
  countriesReferenceData -> australia [label="HAS_COUNTRY"]

  china [label="China (Country)"]
  countriesReferenceData -> china[label="HAS_COUNTRY"]
}

【问题讨论】:

    标签: graphviz dot graph-visualization


    【解决方案1】:

    您可以尝试添加

    splines=true;
    overlap=prism;
    

    而不是 nodesep=2; 并使用 neato 而不是 dot 呈现图形。这将导致更紧凑的布局标签确实与某些节点重叠,并且基于记录的节点彼此非常接近。

    请注意,尽管您可能永远无法通过使用 graphviz 获得完美的数据库架构 - 几乎总会有一些交叉边缘可以以更好的方式布局。手动布局的 db 架构将胜过 graphviz 的输出。

    【讨论】:

    • 最后我使用了 splines=true;重叠=波尔图;模型=子集;这让我走上了正轨。谢谢!
    • 非常好,肯定更好!
    猜你喜欢
    • 2012-03-03
    • 2011-12-16
    • 1970-01-01
    • 2012-09-09
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2012-07-02
    • 1970-01-01
    相关资源
    最近更新 更多