On 03.04.2012 17:58, Martin Bartosch wrote:
I don't think that it is a good idea to create indexes on LOBs. Is it
possible to create a sha1 hash of the LOB and use it as an index key?
Additionally we can generally forbid TEXT columns as index columns.
well, the context is used for a lot of things, it's the curse of having the 
flexibility of the workflow engine. It gives you a lot of freedom, but also 
introduces unpleasant side effects like this one.

Example for fair use: Default API function list_my_certificates() joins over 
three context entries

Speaking of that, I don't find too many instances where such joins are actually 
used - possibly we could work around that. I need to think about it for a while.

I dont know if this is easy to implement and it will certainly need some rework, but whats about having two contexts (or context tables), one for "scalar" data and for blobs?

Oli

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel

Reply via email to