blocks|key|1191206|text|这两种语法形式有点令人困惑，因为它们颠倒了数字：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1191207|LIMIT+<skip>,+<count>|code-block|syntax|javascript|1191208|等同于：|1191209|LIMIT+<count>+OFFSET+<skip>|1191210|它与MySQL和PostgreSQL的语法兼容。MySQL支持这两种语法形式，它的docs声明第二种带偏移量的语法是为了提供与PostgreSQL的兼容性。PostgreSQL+docs表明它只支持第二种语法，而SQLite's+docs则表明它同时支持这两种语法，并建议使用第二种语法以避免混淆。|offset|length|1191211|顺便说一句，使用LIMIT而不先使用ORDER+By并不一定能得到您想要的结果。实际上，SQLite将以某种顺序返回行，这可能取决于它们在文件中的物理存储方式。但这并不一定意味着它是您想要的顺序。获得可预测顺序的唯一方法是显式使用order+BY。|1191212|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.1/en/select.html|1|http://www.postgresql.org/docs/current/static/queries-limit.html|2|https://www.sqlite.org/lang_select.html#limitoffset^0|0|0|0|0|15|4|0|2H|4|1|2Y|D|2|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|16|8|@]|9|@$M|17|N|18|1|19]|$M|1A|N|1B|1|1C]|$M|1D|N|1E|1|1F]]|A|$]]|$1|O|3|P|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]|10|$5|T|U|V|A|$W|11]]]]

The two syntax forms are a little confusing because they reverse the numbers:

<pre><code>LIMIT &lt;skip&gt;, &lt;count&gt;
</code></pre>

Is equivalent to:

<pre><code>LIMIT &lt;count&gt; OFFSET &lt;skip&gt;
</code></pre>

It's compatible with the syntax from MySQL and PostgreSQL. MySQL supports both syntax forms, and its <a href="http://dev.mysql.com/doc/refman/5.1/en/select.html" rel="noreferrer">docs</a> claim that the second syntax with OFFSET was meant to provide compatibility with PostgreSQL. PostgreSQL <a href="http://www.postgresql.org/docs/current/static/queries-limit.html" rel="noreferrer">docs</a> show it only supports the second syntax, and <a href="https://www.sqlite.org/lang_select.html#limitoffset" rel="noreferrer">SQLite's docs</a> show that it supports both, recommending the second syntax to avoid confusion. 

By the way, using LIMIT without first using ORDER BY may not always give you the results you intend. In practice, SQLite will return the rows in some order, probably determined by how they're physically stored in the file. But this doesn't necessarily mean it's in the order you want. The only way to get a predictable order is to use ORDER BY explicitly.

blocks|key|1191244|text|我做了一些测试，在性能上没有区别。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1191245|这只是为了与其他sql语言兼容。|1191246|两个版本的运行时间相同。|1191247|我用table1制作了100000行的sqlite+db。我运行下一个测试|1191248|long+timeLimitOffset+=+0;
long+timeLimitComma+=+0;
for+(int+i+=+0;+i+<+100000;+i%2B%2B)
{
+++//first+version
+++timeLimitOffset+%2B=+SqlDuraction("Select+*+from+table1++order+by+col1+LIMIT+"+%2B+(i+%2B+1)+%2B+"+OFFSET+"+%2B+(1001+-+i)+%2B+"");
+++//+second+version
+++timeLimitComma+%2B=+SqlDuraction("Select+*+from+table1+order+by+col1+LIMIT+"+%2B+(1001+-+i)+%2B+"+,+"+%2B+(i+%2B+1)+%2B+"");
}|code-block|syntax|javascript|1191249|时间变化为0.001秒|1191250|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I made some tests and there is no difference in performance.

That is only for compatability with other sql languages.

Running time of both versions is same.

I made sqlite db with table1 with 100000 rows. I run next test

<pre><code>long timeLimitOffset = 0;
long timeLimitComma = 0;
for (int i = 0; i &lt; 100000; i++)
{
 //first version
 timeLimitOffset += SqlDuraction("Select * from table1 order by col1 LIMIT " + (i + 1) + " OFFSET " + (1001 - i) + "");
 // second version
 timeLimitComma += SqlDuraction("Select * from table1 order by col1 LIMIT " + (1001 - i) + " , " + (i + 1) + "");
}
</code></pre>

Times vary for 0.001 of a second

I have simple question with Sqlite. What is the difference between this:

<pre><code>Select * from Animals LIMIT 100 OFFSET 50
</code></pre>

and

<pre><code>Select * from Animals LIMIT 100,50
</code></pre>

Sqlite LIMIT / OFFSET query

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个关于Sqlite的简单问题。这两者的区别是什么：Select * from Animals LIMIT 100 OFFSET 50和Select * from Animals LIMIT 100,50

问Sqlite限制/偏移查询
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Sqlite限制/偏移查询EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Sqlite限制/偏移查询
EN