Hi Scott, OrientDB 2.0.8 ETL already fixed this problem by supporting \r and \n inside strings.
Best Regards, Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB http://about.me/luca.garulli On 14 May 2015 at 21:32, Scott Orr <[email protected]> wrote: > Actually, we now think it's probably EOL's/CR's inside some of the text > fields. We're not sure if there's a way around this problem using the ETL > tool. > > > Scott > > > On Thursday, May 14, 2015 at 12:34:04 PM UTC-4, Scott Orr wrote: >> >> After having trouble loading data via SQL commands in pyorient, we >> decided to use the ETL tool. We've now discovered that when a text field >> is over 255 characters, the ETL places only the first 255 characters in the >> correct field in the database, and pushes the remaining text into >> subsequent fields. Is there any fix for this? >> >> >> Thanks again, >> >> Scott >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
