This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
It would be nice if Lightspeed could Trim strings of white space when fetched from the database. You insert "HELLO" You get back "HELLO " Unless there is another way I dont know about? |
|
|
|
|
We can't strip whitespace because it might be intentional (if you insert "HELLO " then you'll want to get "HELLO " back!). It sounds like the database is inserting that whitespace, which suggests a database issue. Is the column declared as fixed size (e.g. NCHAR(20) rather than NVARCHAR(20))? |
|
|
|
|
The Columns are NVARCHAR(50) but MS SQL still puts the white space at the end?? Go figure. Perhaps I converted this column from NCHAR. But that doesnt explain why new items are padded. |
|
|
|
|
That's weird. You can probably use the LightSpeed logger and/or SQL Profiler to determine whether the problem is happening before the insert stage (i.e. the app is sending padded data), or whether it's SQL Server mangling the values during the insert. If it's the latter, sorry, no idea what would cause that... |
|
|
|
