Opened 13 years ago

Closed 13 years ago

#729 closed defect (fixed)

SQLServerSpatial: nvarchar columns sometimes blank padded.

Reported by: brentrobinson Owned by: brentrobinson
Priority: major Milestone: 3.6.0
Component: SQLServer Spatial Version: 3.6.0
Severity: 2 Keywords: SQL Server 2008 nvarchar character pad
Cc: External ID:

Description

Steps:

Steps:

  • in SQL Server Management studio:
    • create a new database.
    • load the attached script
    • change the using statement to use your datastore
    • run the script to create the fc table.
  • Using the FdoInsert FDO API command, add a feature to the fc class. Set the name to 'feat1'.
  • Go back to SQL Server Management studio and run the following:
    use <your datastore name>;
    select 'X' + name + 'X' from dbo.fc;

The name value is padded with spaces, e.g.: 'Xfeat1 X'

name is an nvarchar so its values shouldn't get padded.

Attachments (1)

blankpadding.sql (537 bytes ) - added by brentrobinson 13 years ago.

Download all attachments as: .zip

Change History (2)

by brentrobinson, 13 years ago

Attachment: blankpadding.sql added

comment:1 by brentrobinson, 13 years ago

Resolution: fixed
Status: newclosed

Revision: 5833 Author: brentrobinson Date: 1:41:21 PM, Thursday, November 25, 2010 Message: Ticket#729: Set SQL type to varying character when bind variable is variable length string.


Modified : /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/ODBCDriver/bind.c

Note: See TracTickets for help on using tickets.