When Iron Speed Designer creates a table grid with a clickable column, the appropriate SQL query performs the underlying database sorting operation. The sorting performed is generally alphabetic for most fields. The issue arises as to what the appropriate alphabetic sorting is for a given character set. For example, a result set may be sorted differently depending on the character set used for the sorting.
In Microsoft SQL Server 2000, collation can be set at various levels – the database level, the table level and the field level. There is an implied inheritance relationship among these. For example, if field level collation is not defined, the table-level collation is used. If the table collation is not defined, it will inherit from the database.
In an English language environment, SQL queries created by Iron Speed Designer sort properly with all Microsoft SQL Server collation sequences, including these:
SQL_Latin1_General_CP1_CI_AS
Latin1_General_BIN
Korean_Wansung_CI_AS
|
Microsoft SQL Server 2000 |
In-line SQL |
Stored Procedure SQL |
|
Database level collation |
Yes |
Yes |
|
Table level collation |
Yes |
Yes |
|
Field level collation |
Yes |
Yes |
|
Microsoft SQL Server 7 |
In-line SQL |
Stored Procedure SQL |
|
Database level collation |
Yes |
Yes |
|
Table level collation |
N/A |
N/A |
|
Field level collation |
N/A |
N/A |
Note: Iron Speed Designer Support for Microsoft SQL Server 7 was discontinued on June 30, 2006.
Some collation sequences are case-insensitive. If a case-insensitive collation sequence is used, then the table search mechanism created by Iron Speed Designer will be case-insensitive since it uses the underlying database to perform the search. If you want your searches to be case-sensitive, be sure to use a case-sensitive collation sequence in your database.