Strange behavior of ODocument.getOriginalValue()

[PhantomYdn]

Expected behavior and actual behavior

It seems pretty natural return current value on getOriginalValue() if value of a field was not actually changed. But ODocument returns null in this case.

Steps to reproduce the problem

Create a hook with onRecordAfterUpdate(). Check getOriginalValue() of field B of just updated document due to some changes in field A.

Important Questions

Do you see any problems to make it more natural/logical?

Runninng Mode

• Embedded, using PLOCAL access mode
• Embedded, using MEMORY access mode
• Remote

OrientDB Version

• v2.1.18

Operating System

• Linux

Java Version

• 8

[luigidellaquila]

hi @PhantomYdn

IMHO it makes sense, but of course it changes the current behavior (maybe someone is relying on it...)

Guys, maybe we can consider it in 3.0?

Thanks

Luigi

[tglman]

I think we rely on it in few cases, we will check it.