Oops!
Big trouble, TOracleObject Get/SettAttr work improperly with Oracle Number type when precision exceeds precision of Double (15) because those methods ALWAYS convert them to the Double.
What a heck, how can I work with my objects in case when attributes have precision more than 15. Why this situation is handled on TOracleQuery level (converting to string) if precision exceeds TOraSession.Preferences.FloatPrecision and not in case of objects.
Anybody have a solution for that? Changing database obects definition is not an option. [
Linked Image]