<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Docker on Deep Fried Code</title><link>http://deepfriedcode.blog/tags/docker/</link><description>Recent content in Docker on Deep Fried Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 25 Jun 2026 11:25:58 -0400</lastBuildDate><atom:link href="http://deepfriedcode.blog/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Dictionary Website, Part 2: Database Design</title><link>http://deepfriedcode.blog/posts/dictionary-website-part-2/</link><pubDate>Thu, 25 Jun 2026 11:25:58 -0400</pubDate><guid>http://deepfriedcode.blog/posts/dictionary-website-part-2/</guid><description>&lt;p&gt;The first step in building the dictionary is data design. I will be using Postgress as a SQL relational database,
and using PgAdmin to assist in the design of the tables and their relationships.&lt;/p&gt;
&lt;h2 id="building-the-database"&gt;Building the Database&lt;/h2&gt;
&lt;p&gt;My choice for core technology underpinning the data of the website will be a relational database.
Due to the relational nature of language data, especially for my features which will include words in-situ,
as well as translations from english to sourashtra and vice-versa, a database is perfectly suited to the task.
Moreover, there are database utilities that will allow for search and even fuzzy matching, so stay tuned for that later!&lt;/p&gt;</description></item></channel></rss>