<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: dangardan</title><link>https://news.ycombinator.com/user?id=dangardan</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 15 Apr 2026 10:36:33 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=dangardan" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by dangardan in "Found a simple tool for database modeling: dbdiagram.io"]]></title><description><![CDATA[
<p>That's a good point, but to extend my situation, it's a client database I've been asked to transform. The map is indeed difficult to grok all in one, but using different views that come out of the box in yEd, along with some basic rules such as "make all nodes with the word 'cust' yellow", it's been surprisingly effective at exploring the schema.</p>
]]></description><pubDate>Sun, 27 Apr 2025 20:55:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=43815058</link><dc:creator>dangardan</dc:creator><comments>https://news.ycombinator.com/item?id=43815058</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43815058</guid></item><item><title><![CDATA[New comment by dangardan in "Found a simple tool for database modeling: dbdiagram.io"]]></title><description><![CDATA[
<p>I had the opposite problem, was given SQL ddl with near 1000 tables and hundreds of constraints, and had to produce the schema map. Ran the ddl and connected it to yEd, and hey presto, schema map!</p>
]]></description><pubDate>Sun, 27 Apr 2025 04:41:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=43809475</link><dc:creator>dangardan</dc:creator><comments>https://news.ycombinator.com/item?id=43809475</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43809475</guid></item></channel></rss>