I've always used a secondary table (1:1 relationship) which contained just the blob data. The parent table would have the metadata for the blob, and possibly other data as required. That way you can fetch in the name, file size, type, etc without fetching in the blob until needed.
On Wed, Oct 2, 2019 at 8:02 PM Lon Varscsak <lon.varsc...@gmail.com> wrote: > Hey all, > > I have a blob column in an entity, but I don't want to always actually load > the blob, just on demand (but I still want to be able to see the other > attributes in the entity). Any best practice here to have the blob be > lazy? > > Thanks, > > Lon >
