Bug report #8327
MSSQL provider overwrites username in table creation
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  Nathan Woodrow | ||
| Category: | Data Provider/MSSQL | ||
| Affected QGIS version: | 1.8.0 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 17118 |
Description
When loading data into MSSQL through the MSSQL data provider, the name of the file begins dbo.tableName, even though that is not the name of the user.
What I would expect, and we require for integrity of our database, is the name of the table to start with the name of the user who created it.
Example: User 'planning' logs into SQL Server through SQL Server Management Studio, ArcMap, or SHP2SQL. Each of the tables they import through those tools will be named planning.tableName
Associated revisions
Dropping on mssql schema items should import to that schema (fix #8327)
History
#1
Updated by Matthew Baker over 11 years ago
Note this loading data is done by 'drag and drop' into the MSSQL Database.
#2
Updated by Nathan Woodrow over 10 years ago
- OS version deleted (
7) - Operating System deleted (
Windows) - Target version set to Future Release - High Priority
- Category set to Data Provider/MSSQL
#3
Updated by Nathan Woodrow over 9 years ago
Is that the expected outcome though. I guess it should go into the schema it was dropped onto if you have write permissions there.
#4
Updated by Nathan Woodrow over 9 years ago
- Assignee changed from Tamas Szekeres to Nathan Woodrow
- Status changed from Open to Feedback
#5
Updated by Giovanni Manghi about 9 years ago
- Status changed from Feedback to Open
#6
Updated by Nyall Dawson almost 9 years ago
- Status changed from Open to Closed
Fixed in changeset 6efe1eb86bf0a4a3a4161fb377401ca6e5ed42bf.