Avoid changed data immediately resorted by 'ORDER BY'

When an 'ORDER BY' clause exists, this sort order should remain until a new query is posted. Edited data should not be resorted immediately after posting a record - this behaviour interferes manual record changing (e.g. when copying a field value to the next record in the query result set).
This issue should be solved at least for temporary indexes with 'ORDER BY' by introducing an Option 'Fixed' for those indexes or, even better, making this the default behaviour (like MySQL etc.).

47 votes

Vote 0 votes Vote Vote

Vote

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

You have left! (?) (thinking…)

anonymous shared this idea · Sep 06, 2008 · Flag idea as inappropriate… · Admin →

3 comments

Add a comment…

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Submitting...

Martin commented · Jun 23, 2011 · Flag as inappropriate · Delete

Similar problem with Skip and ISAM access - I have to store the next record and GoTo it.
Martin commented · Jun 23, 2011 · Flag as inappropriate · Delete

This is where I have to store all of the record numbers and go to next record - not possible in SQL but is in ISAM.
BobScott commented · Sep 08, 2008 · Flag as inappropriate · Delete

This is a really good idea and would be very helpful.

Feedback:

Avoid changed data immediately resorted by 'ORDER BY'

3 comments

Feedback

General

Knowledge Base and Helpdesk

Searching

Give feedback

advantage