Thread: ASK about SQL

ASK about SQL

From
ali nas
Date:
Dear all,
   HELP me PLZ............................................................................................

I'm used this SQL command :       "" SELECT ean FROM icitem WHERE ean in
(4902715720005,4909411012151,4909411010164,4902715688718,4902715731605,4909411008864,4909411010188,4909411010126,4909411010140,490941101

2052,4902715720104,4909411010089,4909411010201,0,0); """";
 


The FILE content :                                   but the result is :
                      ean                                                                  ---------------
                                         
 
4902715720005                                         4902715720005
4909411012151                                         4902715720104
4909411010164                                         4902715688718
4902715688718                                         4902715731605
4902715731605                                         4909411008864
4909411008864                                         4909411010089
4909411010188                                         4909411010126
4909411010126                                         4909411010140
4909411010140                                         4909411010164
4909411012052                                         4909411010188    
4902715720104                                         4909411010201
4909411010089                                         4909411012052
4909411010201                                         4909411012151    


that is different RESULT with the input !!! what must I do if i dont want POSTGRES not ORDER my SELECT data ????

THX's

     
________________________________________________________ 
Kunjungi halaman depan Yahoo! Indonesia yang baru! 
http://id.yahoo.com/


Re: ASK about SQL

From
"Phillip Smith"
Date:
Do you mean you want it to order it in the same order as you've listed them
in the IN condition?


-----Original Message-----
From: pgsql-sql-owner@postgresql.org [mailto:pgsql-sql-owner@postgresql.org]
On Behalf Of ali nas
Sent: Thursday, 31 May 2007 17:57
To: pgsql-sql@postgresql.org
Subject: [SQL] ASK about SQL

Dear all,
   HELP me
PLZ.........................................................................
...................

I'm used this SQL command :       "" SELECT ean FROM icitem WHERE ean in
(4902715720005,4909411012151,4909411010164,4902715688718,4902715731605,49094
11008864,4909411010188,4909411010126,4909411010140,490941101
2052,4902715720104,4909411010089,4909411010201,0,0) ; """";


The FILE content :                                   but the result is :
                      ean 
---------------
4902715720005                                         4902715720005
4909411012151                                         4902715720104
4909411010164                                         4902715688718
4902715688718                                         4902715731605
4902715731605                                         4909411008864
4909411008864                                         4909411010089
4909411010188                                         4909411010126
4909411010126                                         4909411010140
4909411010140                                         4909411010164
4909411012052                                         4909411010188
4902715720104                                         4909411010201
4909411010089                                         4909411012052
4909411010201                                         4909411012151


that is different RESULT with the input !!! what must I do if i dont want
POSTGRES not ORDER my SELECT data ????

THX's


________________________________________________________
Kunjungi halaman depan Yahoo! Indonesia yang baru!
http://id.yahoo.com/

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to      choose an index scan if your joining column's
datatypesdo not      match 


*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments


Re: ASK about SQL

From
"Phillip Smith"
Date:
Yes, you can order it the same as how you've listed in the IN condition, but
you need to use the ORDER BY clause... Essentially you just need to pass the
same list to both IN and ORDER BY but with some slightly different
formatting...

SELECT    ean
FROM        icitem
WHERE ean IN (4902715720005, 4909411012151, 4909411010164, 4902715688718,
4902715731605, 4909411008864, 4909411010188, 4909411010126, 4909411010140,
4909411012052, 4902715720104, 4909411010089, 4909411010201, 0)
ORDER BY    CASE WHEN ean = 4902715720005 THEN '1'    WHEN ean = 4909411012151 THEN '2'    WHEN ean = 4909411010164
THEN'3'    WHEN ean = 4902715688718 THEN '4'    WHEN ean = 4902715731605 THEN '5'    WHEN ean = 4909411008864 THEN '6'
 WHEN ean = 4909411010188 THEN '7'    WHEN ean = 4909411010126 THEN '8'    WHEN ean = 4909411010140 THEN '9'    WHEN
ean= 4909411012052 THEN '10'    WHEN ean = 4902715720104 THEN '11'    WHEN ean = 4909411010089 THEN '12'    WHEN ean =
4909411010201THEN '13'    WHEN ean = 0 THEN '14' 
;


-----Original Message-----
From: ali nas [mailto:ali_llg21@yahoo.com]
Sent: Thursday, 31 May 2007 18:57
To: Phillip Smith
Subject: Hal: [SQL] ASK about SQL

YES, I don't care with with ORDER BY clause. beacuse i just want what the
data INPUT as like that the data OUTPUT ,so INPUT listed = OUTPUT listed.
so there isn't way in POSTGRES  to do like this ??

----- Pesan Asli ----
Dari: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Kepada: ali nas <ali_llg21@yahoo.com>
Terkirim: Kamis, 31 Mei, 2007 3:44:12
Topik: RE: [SQL] ASK about SQL


You will need to explicitly tell Postgres what order you want it in - unless
you tell PG the order you want with an ORDER BY clause, it assumes you don't
care.

I can't recall 100% the exact syntax for the ORDER BY in your case, but
someone else more with it than me at the moment will be able to... Hang
tight! :)


-----Original Message-----
From: ali nas [mailto:ali_llg21@yahoo.com]
Sent: Thursday, 31 May 2007 18:31
To: Phillip Smith
Subject: Hal: [SQL] ASK about SQL

THX's for answered my question.

YES, i want POSTGRES just do SELECT in the IN condition. add clue, POSTGRES
will show the SELECT data which POSTGRES find first. I dont wanna like that.
So what will I do ??


*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by
Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments


________________________________________________________
Kunjungi halaman depan Yahoo! Indonesia yang baru!
http://id.yahoo.com/


*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments