Sqlite insert and read order will always be same?

Question

0.00/5 (No votes)

See more:

I insert data into SQLite table using "INSERT INTO.." statement
I read data from table using SELCT "FieldName" from "TableName" (that is without using ORDER BY)
=> Doubt is, whehter the read order will be same as insert order?? I expect the data in same order that is inserted?? Should i add an index field in table and use ORDER by for ensuring the order???

What I have tried:

When i tried usually get in the same order as that in which it is inserted? Will it always be like that?

Posted 19-Nov-18 22:23pm

dilsdgr8

Updated 19-Nov-18 22:31pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2018-11-19T22:32:00

Solution 1

No, it doesn't have to be. The only way to be sure of an output order is to use an ORDER BY clause and reference a column that provides the order: an IDENTITY column, or a timestamp.

As you add and remove rows from yoru DB, it leaves "gaps" in the data, which can be filled later to prevent enlarging the file. This can reorder data, and an "implicit order" from your INSERT should never be relied upon. If you need a specific order, then always provide an ORDER BY clause.

Posted 19-Nov-18 22:32pm

OriginalGriff

Comments

dilsdgr8 21-Nov-18 2:39am

In my case i am not deleting any entry. Only inserting. In this case, can I rely on the order

OriginalGriff 21-Nov-18 3:13am

Not necessarily, no. You may not be deleting rows *yet*, but ...
If you want a specific order, always use ORDER BY.

dilsdgr8 21-Nov-18 4:47am

Thanks..
my table cotains one field with large size binary data.. When i give order by, the memory used by application is increased drastically..