quote:

---

Originally posted by deepakdinakaran

Origin Ver. and Service Release (Select Help-->About Origin): Origin 2018, 64 bit, SR 1
Operating System:Windows 8.1

Hello,

I use origin to import data from database (Postgresql). 1D array are stored in the database in the following format {{1,2,3,4,5}}. When I try to access similar array data, origin does not give the complete data points, rather it gives incomplete data import like {{1,2,3

I noticed this behavior for large datasets. When I import around 60 datapoints (ex.{{1,2,3…60}}), origin exactly imports as {{1,2,3…60}}. But when I try to import more than 150 datapoints (ex. {{1,2,3..200}}, it results in incomplete data import as mentioned before.

This is my first issue, and the second issue is the imported data has more numbers after decimal point, which is not expected. The data in the database has only 6 decimal places but origin imports data with more than 10 decimal places. This is observed only while importing array data.

Please refer to the attached picture for a sample import. It would be great to have suggestions.

Thank you and Best regards,
Deepak

---

                                          &&&&&&&&&
                                        &&&
                                       &&
                                      &  _____ ___________
                                     II__|[] | |   I I   |
                                    |        |_|_  I I  _|
                                   < OO----OOO   OO---OO
**********************************************************

quote:

---

Originally posted by cpyang

We need a little bit more information since the screen showed data imported as text in column C.

CP

---

quote:

---

Originally posted by Chris D

Hi,
By testing via copy and paste of long strings, Origin reports that the maximum total length of string data in a cell is 3799 characters and after that, Origin will truncate data after that length.

The additional decimal places are the result of the inability to perfectly represent exact floating point values that is not limited to Origin but is a general issue with most modern computer systems. If you are curious, the following link explains it quite well. It's definitely a good read for the intellectually curious.
https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html

Perhaps you can truncate the numeric at the server as convert to string/text type there. Experiment.



Thanks,
Chris Drozdowski
Originlab Technical Support

---