Sort

former_member386202 — Fri, 23 Mar 2007 08:31:20 GMT

Hi friends,

can u plz tell me the diffrence between sort and order by

thanks *& regards,

prashant

Re: Sort

Former Member — Fri, 23 Mar 2007 08:33:09 GMT

SORT is for Internal tables.

ORDER BY is used in context of a DATABASE table.

ORDER BY is obsolete. Use SORT statement instead.

Both does the same .

Regards,

Ravi

Re: Sort

Former Member — Fri, 23 Mar 2007 08:35:21 GMT

hi,

Order by is included in select statement while fetching records from internal table.

An intenral table is sorted by using Sort statement.

Order by statement in Select will deprove the performance. so, better not use it.

Regards,

Sailaja.

Re: Sort

Former Member — Fri, 23 Mar 2007 08:45:44 GMT

Hi Prashanth....

ORDER BY Clause is used in the SELECT Statement when retrieving the data from the data from database.

if we use ORDER BY Clause the data is sorted at the database server level and brought to the application server...

SORT is used to sort the contents of the Internal table.

It is recommended to use SORT than ORDER BY Clause because we need to reduce the load on the database server so we have to read the data from the database and then sort it using SORT .....

Reward points if useful......

Suresh......

Re: Sort

Former Member — Fri, 23 Mar 2007 08:49:06 GMT

Re: Sort

Former Member — Fri, 23 Mar 2007 08:55:53 GMT

order by claus is used in select statement in this form.

SELECT result

FROM source

INTO|APPENDING target

[[FOR ALL ENTRIES IN itab] WHERE sql_cond]

...

SELECT - sort_key

Syntax

... ORDER BY { {PRIMARY KEY}

| { {col1|a1} ASCENDING

{col2|a2} ASCENDING ...}

| (column_syntax) } ... .

Alternatives:

1. ... ORDER BY PRIMARY KEY

2. ... ORDER BY {col1|a1} ASCENDING

{col2|a2} ASCENDING ...

3. ... ORDER BY (column_syntax)

Effect:

The addition ORDER BY sorts the resulting set by the content of the specified column. The order of the rows in the result set refers to all columns that are not listed after ORDER BY, is undefined, and can be different in repeated executions of the same SELECT statement.

The addition ORDER BY can only be used with the addition PRIMARY KEY at the same time as the addition FOR ALL ENTRIES of the WHERE condition.

Note:

If a sorted resulting set is assigned to a sorted internal table, the internal table is sorted again according to the sorting instructions.

Alternative 1

... ORDER BY PRIMARY KEY

Effect:

If all columns are specified (by the entry of * after SELECT), and a single database table is specified after FROM (rather than a view or a join expression), the addition PRIMARY KEY can be used to sort the resulting set in ascending order according to the content of the primary key of this database table.

The addition PRIMARY KEY cannot be specified if a view or a join expression is statically specified after FROM. If a view or a join expression is specified after FROM in the dynamic specification dbtab_syntax, the data is sorted by all columns of the resulting set.

Alternative 2

... ORDER BY {col1|a1} ASCENDING

{col2|a2} ASCENDING ...

Effect:

For any column specifications after SELECT, a list of columns can be entered after ORDER BY, by which the resulting set should be sorted. Only columns that are listed after SELECT can be entered. Columns can be specifieddirectly using the column names col1 col2 ..., or the alternative column names a1 a2 .... The latter is required if you want to sort by columns that are specified as aggregate expressions.

The additions ASCENDING and DESCENDING determine whether the rows are sorted in ascending or descendding order. If neither addition is specified, the sorg is performed in ascending order. The priority of sorting is based on the order in which the components col1 col2... or a1 a2 ... are specified.

Pooled and cluster tables cannot be sorted by all types of column. Columns specified after ORDER BY cannot be of the type LCHAR, LRAW, STRING, or RAWSTRING.

Note:

If single columns are specified in the addition ORDER BY, the statement SELECT bypasses the SAP buffering.

Alternative 3

... ORDER BY (column_syntax)

Effect:

As an alternative to static column specification, a bracketed data object column_syntax can be specified, which either contains the syntax of the list of columns or is initial when the statement is executed. The addition PRIMARY KEY cannot be specified in column_syntax. For column_syntax, the same applies as for the dynamic specification of columns after SELECT. If the content of column_syntax is initial, the addition ORDER BY is ignored.

Note:

For performance reasons, sorting should only be performed in tha databases system if the sort is supported by an index.

Example:

Selecting the database table SFLIGHT in a method, whereby the sort criterion is transferred as an input parameter. In this case, the user must enter the criterion using the correct syntax on the selection screen/>. In a proper application, you would normally prepare an input help using a selection list.

TYPES sflight_table_type TYPE TABLE OF sflight.

CLASS handle_sflight DEFINITION.

PUBLIC SECTION.

CLASS-METHODS select_sort_sflight

IMPORTING sort_crit TYPE string

EXPORTING sflight_tab TYPE sflight_table_type

RAISING cx_sy_dynamic_osql_error.

ENDCLASS.

PARAMETERS p_sort(40) TYPE c.

DATA: s_sort TYPE string,

result_tab TYPE sflight_table_type.

TRY.

s_sort = p_sort.

handle_sflight=>select_sort_sflight(

EXPORTING sort_crit = s_sort

IMPORTING sflight_tab = result_tab ).

CATCH cx_sy_dynamic_osql_error.

MESSAGE `Wrong sort criterium!` TYPE 'I'.

ENDTRY.

CLASS handle_sflight IMPLEMENTATION.

METHOD select_sort_sflight.

SELECT *

FROM sflight

INTO TABLE sflight_tab

ORDER BY (sort_crit).

ENDMETHOD.

ENDCLASS.

the sort is

according to the locale of the current text environment. If AS TEXT is not specified, text-type components are sorted according to the coding in the code page of the current text environment. This specification can be overwritten for individual text-type components in the explicit sort key sort_key. The text environment is set when an internal session is opened, or using the statement SET LOCALE.

Notes

Sorting without the AS TEXT addition is considerably faster than sorting using the addition. If text-type components only contain characters of the ASCII character set, both sort options result in the same sort order and the addition AS TEXT is not necessary.

The result of lexicographic sorting depends on the operating system of the application server. While the sequence of the individual letters that belong to the activated language is the same for all operating systems, there are differences in the characters that do not belong to the alphabet of the activated language. When sorting whole words, there are also slight differences even if only using letters from the alphabet of the activated language. The order of upper and lower case letters also depends on the operating system.

For the AS TEXT addition to function correctly, the profile parameter install/collate/active must not have the value 0.

The use of the AS TEXT addition normally renders the statement CONVERT TEXT superfluous.

Addition 3

...STABLE

Effect

You can use STABLE to ensure a stable sort order. This means that the order of lines, which is the same in the sort key, remains unchanged after sorting. Without the STABLE addition, the order is not preserved and repeated sorting of a table by the same sort key changes the order each time the table is sorted.

Example

Sorting a hashed table text_tab by the order in the code page and according to the locale of the current text environment. If a Western European text environment is set, sorting results in the orders Miller, Moller, Muller, Möller, or Miller, Moller, Möller, Muller (also see the example for SET LOCALE).

DATA text_tab TYPE HASHED TABLE OF string

WITH UNIQUE KEY table_line.

INSERT: `Muller` INTO TABLE text_tab,

`Möller` INTO TABLE text_tab,

`Moller` INTO TABLE text_tab,

`Miller` INTO TABLE text_tab.

SORT text_tab.

PERFORM write_text_tab.

SORT text_tab AS TEXT.

PERFORM write_text_tab.

FORM write_text_tab.

FIELD-SYMBOLS TYPE string.

LOOP AT text_tab ASSIGNING .

WRITE / .

ENDLOOP.

SKIP.

ENDFORM.

SORT itab - sort_key

Syntax

... BY comp1 ASCENDING

comp2 ASCENDING

... .

Extras:

1. ... ASCENDING|DESCENDING

2. ... AS TEXT

Effect

If you specify a sort key with the addition BY, sorting is not done according to the table key, but according to the comp1 comp2 ... component specified after it. The components are specified as described under specification of components, with the limitation that the number of coponents that can be specified is limited to 250. The sort priority is according to the sequence in which the components comp1 comp2 ... are specified from left to right.

In the case of internal tables with a header line, field symbols can also be specified outside of classes for comp1 comp2 .... If a component of the header line or the entire header line is assigned to a field symbol during execution of the statement, sorting will take place according to the respective component or the entire line. If no data object is assigned to a field symbol, sorting will take place according to the respective component or the entire line. If no data object is assigned to a field symbol, the specification will be ignored. If a different data object is assigned to a field symbol, there will be an exception that cannot be handled.

Notes

Instead of using field symbols for dynamic component specifications, you should use the option to specify bracketed, character-type data objects that contain the name of the components.

Addition 1

... ASCENDING|DESCENDING

Effect

If, after a component comp1 comp2 ..., none of the additions ASCENDING or DESCENDING is specified, the predefined sort sequence is adopted. If one of the additions ASCENDING or DESCENDING is specified, it will override the specification for this component.

Addition 2

... AS TEXT

Effect

If, after a text-type component comp1 comp2..., the addition AS TEXT is not specified, the predifined specification is adopted. If, after a text-type component, the addition AS TEXT is specified, it overrides the predefined specifcation for this component. In the case of non-text-type components, AS TEXT cannot be specified.

this is complete information.

topic Re: Sort in Application Development and Automation Discussions

Sort

Re: Sort

Re: Sort

Re: Sort

Re: Sort

Re: Sort