This is a discussion on [ psqlodbc-Bugs-1000759 ] SQLGetInfo(SQL_NULL_COLLATION) returns SQL_NC_END instead of SQL_NC_HIGH within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> Bugs item #1000759, was opened at 2006-10-19 09:53 You can respond by visiting: http://pgfoundry.org/tracker/?func=d...oup_id=1000125 Category: None Group: None Status: ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Bugs item #1000759, was opened at 2006-10-19 09:53 You can respond by visiting: http://pgfoundry.org/tracker/?func=d...oup_id=1000125 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Dmitriy Ivanov (divanov) Assigned to: Nobody (None) Summary: SQLGetInfo(SQL_NULL_COLLATION) returns SQL_NC_END instead of SQL_NC_HIGH Initial Comment: With the ANSI dirver 08.02.0103, I get SQLGetInfo(SQL_NULL_COLLATION) => 4, i.e. SQL_NC_END. This obviously contradicts to actual results and PG documentation Part VI. Reference > SQL Commands > SELECT: The null value sorts higher than any other value. In other words, with ascending sort order, null values sort at the end, and with descending sort order, null values sort at the beginning. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=d...oup_id=1000125 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |