Field data difference between TQuery and TUniQuery

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
bgacorrie
Posts: 9
Joined: Fri 28 Aug 2015 16:55

Field data difference between TQuery and TUniQuery

Post by bgacorrie » Wed 09 Dec 2015 22:19

Using the same sql command in both attached to an MSSQl server database.
I am seeing training spaces on some data in specific fields but not in others with TUniQuery or TUniTable. TQuery displays it fine.

There is no training spaces in the data.

Fields are varchars and it is not all of the fields just some. Looks to be 6 characters no mater the length of the data.

Very strange

I must be missing something

bgacorrie
Posts: 9
Joined: Fri 28 Aug 2015 16:55

Re: Field data difference between TQuery and TUniQuery

Post by bgacorrie » Thu 10 Dec 2015 16:11

More info on this.

Tried this with Oracle and it works fine. Must be the SQLProvider.
I am connecting to MSSQL 2005

bgacorrie
Posts: 9
Joined: Fri 28 Aug 2015 16:55

Re: Field data difference between TQuery and TUniQuery

Post by bgacorrie » Thu 10 Dec 2015 21:46

I found the cause it was in a script that loaded the data it was loaded as a char type instead of a varchar. not sure why tuniquery and tunitable cared while tquery and ttable didn't but at least I know know.

azyk
Devart Team
Posts: 1119
Joined: Fri 11 Apr 2014 11:47
Location: Alpha Centauri A

Re: Field data difference between TQuery and TUniQuery

Post by azyk » Fri 11 Dec 2015 09:09

Please try to compose a small sample reproducing the issue and send it to andreyz*devart*com. Include the scripts for creating the table-source and table-recipient.

Post Reply