FETCH issues

Description

FETCH seems to expect deserialized form of LHS disk record as its input, rather than serialzied form.

This is rather inefficient, especially when dealing with record translation. It also means that fields such as virtual fileposition give random results/read off the end of the input buffer, since deserialize has not filled them in (not sure it knows how).

If fetch's transform expected the serialized form as input instead (as I believe diskread does) then these problems would be sidestepped I think.

Conclusion

None

Activity

Show:

Gavin Halliday December 5, 2017 at 2:27 PM

The problem only occurs if the LHS of the fetch is complex.  E.g. contains PRELOAD/NOFOLD or some other operations.  Their presence prevents the transform being mapped back to the serialized form.

 

The code generator should have spotted that the transform hadn't been mapped properly, and thrown an error.

 

 

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Created November 25, 2017 at 6:58 AM
Updated December 6, 2017 at 11:54 AM
Resolved December 6, 2017 at 11:54 AM

Flag notifications