i do n't under stand the case part please help me

Question

0.00/5 (No votes)

See more:

SELECT ID, name, city, ImageName, ImagePath
FROM aaaa
ORDER BY CASE WHEN ID > 0 THEN
(SELECT MAX(ID)
FROM [dbo].[aaaa]) + 1 ELSE ID END, ID DESC

result
id
0
3
2
1

Posted 11-Apr-13 2:16am

chinmaya parija1

Updated 11-Apr-13 2:56am

v6

Add a Solution

Comments

AmitGajjar 11-Apr-13 8:25am

are you sure this query is correct ? it doesn't surve any purpose.

chinmaya parija1 11-Apr-13 8:42am

yes
the result like this
ID
0
3
2
1

chinmaya parija1 11-Apr-13 8:47am

i want result like this
ID column
0
3
2
1
while desc and
ID column
0
1
2
3
while asc

0 id will be in top whether asc or desc.....

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 · Answer 1 · 2013-04-11T02:26:00

If the row ID is greater than zero, then the query will return the maximum ID value, plus one.
If it isn't, it will return zero.

And it's a stupid thing to do. If it is used in a multiuser environment, it leads to IDs being duplicated occasionally, more frequently is there is any noticeable time period between the use of this code and the actual save of the new record. Intermittent problems like this are a real PITA to find once a database goes live, and should be avoided at all costs. Instead, allocate an id when you save the data, and not before - use the Identity specification if you have to, or use GUIDs instead.