[ psqlodbc-Bugs-1000745 ] SQLStatistics does not return indices based on expression

Bugs item #1000745, was opened at 2006-10-05 09:41
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=10007 45&group_id=1000125

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 3
Submitted By: Dmitriy Ivanov (divanov)
Assigned to: Hiroshi Inoue (hinoue)
Summary: SQLStatistics does not return indices based on expression

Initial Comment:
Driver 08.02.0103 ANSI. After executing

CREATE UNIQUE INDEX employee_name_idx
ON employee (upper(last_name || ' ' || first_name));

I can see employee_name_idx in pgAdminIII, DROP INDEX also works, but SQLStatistics does not mention it.


------------------------------------------------------------ ----------

>Comment By: Hiroshi Inoue (hinoue)
Date: 2006-10-21 03:42

Message:
This was solved together with #100759.

------------------------------------------------------------ ----------

Comment By: Hiroshi Inoue (hinoue)
Date: 2006-10-20 02:07

Message:
Could you try the attached dll at #100759(SQLGetInfo(SQL_NULL_COLLATION) ..) ?

regards,
Hiroshi Inoue

------------------------------------------------------------ ----------

Comment By: Dmitriy Ivanov (divanov)
Date: 2006-10-09 10:44

Message:
RTFM: Checking the "Recognize Unique Indexes" box makes
SQLStatistics return 0 (SQL_FALSE). Sorry about my last
comment.

Nevertheless, indices based on expression still are not
mentioned.

------------------------------------------------------------ ----------

Comment By: Dmitriy Ivanov (divanov)
Date: 2006-10-05 10:46

Message:
Moreover, SQLStatistics returns 1 (SQL_TRUE) in the
NON_UNIQUE column for
1) indices created explicitly via CREATE UNIQUE INDEX,
2) implicitly created primary keys.

------------------------------------------------------------ ----------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=10007 45&group_id=1000125

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq