Bug #43991 | GetSchema on Indexes or IndexColumns fails where index or column names are restr | ||
---|---|---|---|
Submitted: | 31 Mar 2009 17:21 | Modified: | 6 Apr 2009 13:17 |
Reporter: | Tonci Grgin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | OS: | Any | |
Assigned to: | Reggie Burnett | CPU Architecture: | Any |
[31 Mar 2009 17:21]
Tonci Grgin
[31 Mar 2009 19:38]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/70954
[31 Mar 2009 19:39]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/70955
[31 Mar 2009 19:40]
Reggie Burnett
fixed in 5.1.8, 5.2.6+
[6 Apr 2009 13:17]
Tony Bedford
An entry was added to the 5.1.8 and 5.2.6 changelogs: Calling GetSchema() on Indexes or IndexColumns failed where index or column names were restricted. In SchemaProvider.cs, methods GetIndexes() and GetIndexColumns() passed their restrictions directly to GetTables(). This only worked if the restrictions were no more specific than schemaName and tableName. If IndexName was given, this was passed to GetTables() where it was treated as TableType. As a result no tables were returned, unless the index name happened to be BASE TABLE or VIEW. This meant that both methods failed to return any rows.