ORDA: How do you handle BLOB fields?

Product :4D - 4D Server
4D : v17
OS : Windows

When I try to get a record that contains a BLOB field, it is null.
eg. $user := ds.UserAccount.get(1)
$user.Password // (=null if it is from a blob field)

When I try to assign it a blob value, I get an error.
eg. $user.Password := $blob // gets an error

How do you handle BLOB fields in ORDA?

I see in the documentation under
http://livedoc.4d.com/4Dv17/help/Title/en/page9301.html#3783599ORDA
Prerequisites>:

To be able to use ORDA in your 4D databases, you need to make sure
that the following requirements and specifications are respected:

Ouch!

So my choice is either
(1) hybrid programming (mixture of ORDA and traditional) OR
(2) use of Text (base64) field instead of BLOB?

: Tim PENNER

I see in the documentation under
http://livedoc.4d.com/4Dv17/help/Title/en/page9301.html#3783599ORDA
Prerequisites>:

To be able to use ORDA in your 4D databases, you need to make sure
that the following requirements and specifications are respected:

you can use a picture as an encapsulated blob

c.f.

http://doc.4d.com/4Dv16/4D/16.3/BLOB-TO-PICTURE.301-3651678.en.html

If you pass a codec that is not recognized by 4D in codec, a new
codec is recorded dynamically with the ID passed in the parameter. 4D
then returns a picture that encapsulates the BLOB and the OK variable
is set to 1. In this case, to retrieve the BLOB, you will need to use
the PICTURE TO BLOB command with the same custom ID. This particular
mechanism can be used to meet two specific needs:
encapsulation of a BLOB (that is not a picture) into a picture,
loading a picture without using a codec.
The implementation of these mechanisms allows, more specifically, the
creation of “BLOB arrays” via picture arrays. This technique must be
used with caution because, since the arrays are loaded entirely into
memory, working with large sized BLOBs can affect the functioning of
the application.
Note: A BLOB created by the VARIABLE TO BLOB command is managed
automatically; it is not necessary to pass a codec to encapsulate it
since the BLOB is “signed.” In this case, for the opposite operation,
you will need to pass “.4DVarBlob” to the PICTURE TO BLOB command as
the codec ID.