ok,
that sounds great.
btw, the encryption support is done by adding another file to the distro,
not patching, so you only include the file if you need it.
_a
> Hello,
>
>>> Would this be suitable for allowing one to have fields automatically be
>>> encrypted in the database?
>>> This seems like more of a Metabase question, but I have no experience
>>> with Metabase.
>>
>> It's a mix. But it certainly belongs in the entity def. I'll add it.
>>
>>> At first thought, I'd say use mcrypt to encrypt/decrypt the data
>>> automatically to/from the database if the encrypt tag is TRUE in the
>>> entity definition.
>>
>> That's what happens in r1
>
> BTW, I am starting to implement LOB support to Metabase. Passing data to LOBs
> will use input stream objects. These objects will be of classes derived from a
> Metabase input stream class. In the derived classes you can supply data with
> functions that may do all sorts of things link for instance filtering data
> (encrypting, compressing, etc...).
>
> I want to make these input stream objects also work with non-LOB fields to
> promote further reuse. I want to provide basic input stream classes for
> passing data defined statically or from files. I think that is the place for
> you to provide further classes to do other types of other filtering without
> patching Metabase.
>
> Regards,
> Manuel Lemos
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>
|
