<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sqlite on FromDual GmbH</title><link>https://www.fromdual.com/tags/sqlite/</link><description>Recent content in Sqlite 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, 10 Feb 2021 11:49:41 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/sqlite/index.xml" rel="self" type="application/rss+xml"/><item><title>Databases are standardized but in detail they behave different</title><link>https://www.fromdual.com/blog/databases-are-standardized-but-in-detail-they-behave-different/</link><pubDate>Wed, 10 Feb 2021 11:47:20 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/databases-are-standardized-but-in-detail-they-behave-different/</guid><description>&lt;p&gt;For a fancy application we want to query a chunk of rows from a table and therefore we need the minimum and the maximum of the Primary Key of these rows.&lt;br&gt;
Because &lt;a href="https://dev.mysql.com/doc/refman/5.7/en/primary-key-optimization.html" target="_blank" title="Primary Key Optimization"&gt;InnoDB&lt;/a&gt; is an &lt;a href="https://www.orafaq.com/wiki/Index-organized_table" target="_blank" title="Index organized Table"&gt;Index Organized Table&lt;/a&gt; or &lt;a href="https://docs.microsoft.com/en-us/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described?view=sql-server-ver15" target="_blank" title="Clustered and nonclustered indexes described"&gt;Index Clustered Table&lt;/a&gt; we know that this access will use the Primary Key. But to be sure and to be compliant with the standard (and compatible) we use and &lt;code&gt;ORDER BY&lt;/code&gt; on the Primary Key.&lt;/p&gt;</description></item></channel></rss>