<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Type on FromDual GmbH</title><link>https://www.fromdual.com/tags/data-type/</link><description>Recent content in Data Type 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>Wed, 25 May 2016 11:42:20 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/data-type/index.xml" rel="self" type="application/rss+xml"/><item><title>Why you should take care of MySQL data types</title><link>https://www.fromdual.com/blog/why-you-should-take-care-of-mysql-data-types/</link><pubDate>Wed, 25 May 2016 11:42:20 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/why-you-should-take-care-of-mysql-data-types/</guid><description>&lt;p>A customer reported last month that MySQL does a full table scan (FTS) if a query was filtered by a &lt;code>INT&lt;/code> value on a &lt;code>VARCHAR&lt;/code> column. First I told him that this is not true any more because MySQL has fixed this behaviour long time ago. He showed me that I was wrong:&lt;/p></description></item></channel></rss>