Opened 15 years ago
Closed 14 years ago
#432 closed defect (fixed)
SQLServerSpatial cannot support read-only users
| Reported by: | barbarazoladek | Owned by: | brentrobinson |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | FDO API | Version: | 3.3.0 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
A read-only user cannot connect to the SQLServerSpatial. After making connection to the SQL Server, the provider logs the active session in the f_dbopen and that requires insert privileges which the read-only user does not have. The solution: Provider should catch the insefficient privileges error and allow user to connect
Change History (3)
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|
comment:2 by , 14 years ago
| Status: | new → assigned |
|---|
comment:3 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Revision: 5784 Author: brentrobinson Date: 4:41:31 PM, Friday, October 29, 2010 Message: Ticket#432: Modified the SQLServerSpatial and MySQL providers to not insert into f_dbopen when opening a connection on a datastore with metaschema. For the SQLServerSpatial provider, this allows users to open datastores for which they have readonly access.
Modified : /trunk/Providers/GenericRdbms/Src/MySQL/Fdo/FdoRdbmsMySqlConnection.cpp Modified : /trunk/Providers/GenericRdbms/Src/MySQL/Fdo/FdoRdbmsMySqlConnection.h Modified : /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/Fdo/FdoRdbmsSqlServerConnection.cpp Modified : /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/Fdo/FdoRdbmsSqlServerConnection.h