Upon further investigation, we found that the problem is apostrophes--which are the same as single quotes, of course. We have no trouble with them using the ETL tool, but we can't input them using SQL commands (so we can load in our initial data, but we'll have trouble doing updates).
We can escape them in SQL commands using a backslash, but the database retains the backslash, and so we end up with different text if we insert records with SQL than if we do so via the ETL tool. Scott On Wednesday, May 13, 2015 at 1:25:34 PM UTC-4, Amir Khawaja wrote: > > Hi Scott, > > You could Base64 encode and then HTML encode the data. Also, if you are > inserting data using SQL, then you need to remove the \r\n characters in > strings. > > Amir. > > > On Wednesday, May 13, 2015 at 12:11:26 PM UTC-5, Scott Orr wrote: >> >> We're trying to store (short) HTML documents in an Orient database, and >> keep getting errors. Has anyone found a way to do this? >> >> >> 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.
