Opened 15 years ago
Closed 14 years ago
#552 closed defect (fixed)
Managed StringElement garbles the .net string assigned to it
| Reported by: | jng | Owned by: | gregboone |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | FDO API | Version: | 3.4.0 |
| Severity: | 1 | Keywords: | |
| Cc: | External ID: |
Description
Create a ODBC provider connection to MSTest.mdb in the GenericRdbms unit test directory
Execute an IDescribeSchema with:
SchemaName = "Fdo" ClassNames = { <any table in that database> }
The execution will fail, and the provider will report the following message:
Unable to find class '<table name>'
The only thing here is that <table name> has been somehow garbled by the provider, and I am assuming it is trying to execute under this garbled name.
For example: 'Cities' gets turned into 'ቈܮties' by the provider.
Attachments (1)
Change History (5)
comment:1 by , 15 years ago
| Component: | ODBC Provider → GenericRdbms API |
|---|
comment:2 by , 15 years ago
| Priority: | major → critical |
|---|---|
| Severity: | 3 → 1 |
by , 15 years ago
| Attachment: | Program.cs added |
|---|
comment:3 by , 15 years ago
| Component: | GenericRdbms API → FDO API |
|---|---|
| Summary: | ODBC provider garbles the specified class name when using enhanced IDescribeSchema → Managed StringElement garbles the .net string assigned to it |
In writing the attached sample code, I've discovered that the StringElement wrapper class is quite possibly the culprit here.
When you feed a .net string to a new StringElement instance, inspecting the String property (StringElement.String) returns a garbled version of the original string.
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Confirmed that this has been resolved in 3.4.1 RC2
C# source demonstrating the problem