The Oracle relaxed SQL parser has some special use cases for dealing with apostrophes that are not escaped. There is one corner case where if the SQL contains something like:

update "schema"."table" 
  set "field" = 'Nello svolgere la sua attivita', del liquido uticante penetrava nei guanti di sicurezza scottando la pelle dei polsi'
where "ID" = '1' and "field" = '<some prior value>'

The new value for field would be truncated because the sequence of apostrophe followed by comma is seen as the end of the value because the embedded apostrophe is mistakenly not escaped by Oracle.

This applies only to Oracle when configured with EXTENDED max_string_size.