title: 2.1 Syntax not Working in 2.2. Update child record via parent class
body: <p>Hello OrientDB followers,</p>
  
  <p>I have an issue that has been taking up more of my time than i would like to spend on.</p>
  
  <p>In 2.1, I was able to <strong><em>update a parent record and child record from a single command or just the child record via an update of the parent class</em></strong>. However, <strong>in 2.2, it does not work</strong>.. I have used the same exact syntax in both.</p>
  
  <p>Take the following sample data set</p>
  
  <pre><code>create class Users
  create property Users.username
  create property Users.password
  
  create class Devices
  create property Devices.name
  
  insert into Users (username, password) values('johndoe','randompassword')
  
    update users add Devices = [{
              "@type": "d",
              "@class": "Devices",
              "name": "Note 7"
          }]
  </code></pre>
  
  <p>lets say that the Device class record that we just inserted ended up with an rid of #13:0</p>
  
  <p>In version <strong>2.1</strong>, I am able to execute the following syntax below, in order to update the parent and the child record. <strong>It works perfect</strong> </p>
  
  <pre><code>  update users set username = 'johndoethesenior', Devices = [{
              "@type": "d",
              "@rid":   #14:0,
              "@version":1,
              "@class": "Devices",
              "name": "Note 8"
          }] where username = 'johndoe'
  </code></pre>
  
  <p>There lies my issue. In 2.1 it works perfectly. However, <strong>in 2.2, even though i do not get an error and it shows the record as updated, the name on the Devices record does not change from Note 7 to Note 8.</strong></p>
  
  <p>The change on the parent record, does go through and changes from johndoe to johndoethesenior. </p>
  
  <p>I looked through the release notes and changes of 2.1 -> 2.2 and could not find any references to this. </p>
  
  <p>Did i discover a bug, or am I overlooking something that changed in the orient architecture after 2.2 release.</p>
  
  <p>Last note, I have tried this on at least 4 versions of 2.2, on different servers and deployments. All have the same behavior.</p>
  
  <p>Any guidance in the matter would be truly appreciated. </p>
  
  <p>Thanks,</p>