Opened 15 years ago
Closed 15 years ago
#441 closed defect (fixed)
SQLServerSpatial: Propogate up connection errors
| Reported by: | brentrobinson | Owned by: | brentrobinson |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.4.0 |
| Component: | SQLServer Spatial | Version: | 3.4.0 |
| Severity: | 3 | Keywords: | Connection error message |
| Cc: | External ID: |
Description
When connect to SQL Server fails, the error messages retrieved from SQL Server are not propogated up. This ticket will ensure that the messages end up in the exception thrown by the FdoIConnection::Open() implementation.
For example, the provider throws the following when trying to connect to a non-existent SQL Server instance:
No current open database.
This will be changed to :
RDBMS: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Change History (2)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Revision: 4313 Author: brentrobinson Date: 8:16:53 AM, Thursday, December 11, 2008 Message: Ticket#441: propogate up connection error messages from SQL Server to FDO caller.
Modified : /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/ODBCDriver/connect.c Modified : /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/ODBCDriver/get_msg.c