Reserved schema names are not checked, cause unexpected behavior instead of errors
I was creating a custom schema that has to do with some new versioning properties, and I named it "versions". This inadvertently collided with the existing "versions" table name, resulting in the following unexpected behavior. My new properties insi...