<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design on FromDual GmbH</title><link>https://www.fromdual.com/tags/design/</link><description>Recent content in Design on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Fri, 22 Oct 2021 17:17:29 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/design/index.xml" rel="self" type="application/rss+xml"/><item><title>Architecture and Design decisions</title><link>https://www.fromdual.com/blog/architecture-and-design-decisions/</link><pubDate>Mon, 13 Jan 2020 09:00:31 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/architecture-and-design-decisions/</guid><description>&lt;p&gt;When it comes to MariaDB/MySQL Database consulting engagements we often see, that our customers are very confused by many different technologies advertised to them.&lt;/p&gt;</description></item><item><title>Storing BLOBs in the database</title><link>https://www.fromdual.com/blog/storing-blobs-in-the-database/</link><pubDate>Fri, 30 Jun 2017 14:18:07 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/storing-blobs-in-the-database/</guid><description>&lt;p&gt;We have sometimes discussions with our customers whether to store LOBs (Large Objects) in the database or not. To not rephrase the arguments again and again I have summarized them in the following lines.&lt;/p&gt;</description></item><item><title>Using NULL as default values</title><link>https://www.fromdual.com/blog/using-null-as-default-values/</link><pubDate>Thu, 21 Jul 2011 18:35:34 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/using-null-as-default-values/</guid><description>&lt;h2 id="abstract"&gt;Abstract:&lt;/h2&gt;
&lt;p&gt;It is common practice in MySQL table design that fields are declared as &lt;code&gt;NOT NULL&lt;/code&gt; but some non-sense &lt;code&gt;DEFAULT&lt;/code&gt; values are specified for unknown field contents. In this article we show why this behavior is non optimal an why you should better declare a field to allow &lt;code&gt;NULL&lt;/code&gt; values and use &lt;code&gt;NULL&lt;/code&gt; values instead of some dummy values.&lt;/p&gt;</description></item><item><title>Data Warehouse Design</title><link>https://www.fromdual.com/blog/data-warehouse-design/</link><pubDate>Wed, 16 Jun 2021 23:02:43 +0200</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/data-warehouse-design/</guid><description>&lt;p&gt;This is my cheat sheet for dimensional modelling design techniques of a data warehouse (DWH) according to &lt;a href="https://www.amazon.de/Data-Warehouse-Toolkit-Definitive-Dimensional/dp/1118530802" target="_blank"&gt;Kimball/Ross&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>