<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blob on FromDual GmbH</title><link>https://www.fromdual.com/tags/blob/</link><description>Recent content in Blob 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/blob/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>Dumping BLOB's from the MySQL database</title><link>https://www.fromdual.com/blog/dumping-blobs-from-mysql/</link><pubDate>Fri, 22 Apr 2011 13:52:42 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/dumping-blobs-from-mysql/</guid><description>&lt;p&gt;A customer who is handling digital certificates had a problem with one of those. So we had to investigate.&lt;/p&gt;</description></item><item><title>Transactional memory resident tables with PBXT</title><link>https://www.fromdual.com/blog/transactional-memory-resident-tables-with-pbxt/</link><pubDate>Sun, 21 Nov 2010 21:32:18 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/transactional-memory-resident-tables-with-pbxt/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In his &lt;a href="http://www.primebase.org/download/pbxt-uc-2010.pdf" target="_blank"&gt;presentation&lt;/a&gt; about &lt;a href="http://www.primebase.com/" target="_blank"&gt;PBXT&lt;/a&gt; at the &lt;a href="http://www.doag.org/konferenz/doag/2010/" target="_blank"&gt;DOAG Conference 2010&lt;/a&gt; Paul McCullagh was speaking about &lt;a href="https://code.launchpad.net/~paul-mccullagh/pbxt/memory-tables" target="_blank"&gt;memory resident PBXT tables&lt;/a&gt;. They will be available in version 1.1 of the PBXT Storage Engine Plugin. Memory resident PBXT tables should have similar characteristics like normal &lt;a href="http://dev.mysql.com/doc/refman/5.1/en/memory-storage-engine.html" target="_blank"&gt;MySQL &lt;code&gt;MEMORY&amp;lt;/span&amp;gt; tables&amp;lt;/a&amp;gt;. But in addition to the &lt;/code&gt;MEMORY&lt;/span&gt; tables they are transactional and can handle &lt;code&gt;BLOB&amp;lt;/span&amp;gt; and &lt;/code&gt;TEXT&lt;/span&gt; attributes.&lt;/p&gt;</description></item></channel></rss>