Hi Achim, > Unfortunately we would also need the solution for workflow_context. > I don't have the experience how large it could grow, i just imagine > large key lengths of 8192 and corresponding blown up certificate lenghts. > This could be rather dynamic in the future, and the database indexes > should correspond to this.
Personally, I see the context as an opaque datastore and dislike the idea of doing any search queries on the data. I know that we do this at the moment in some places but I would like to see this "searchable context data" in a dedicated mapping/index/search - whatever you would name it - table. In return, we would not need to index the value portion of the context table, as it is never used to search within. > CREATE INDEX wf_context_value_index on workflow_context > workflow_context_value); > CREATE INDEX cert_attributes_value_index on certificate_attributes > attribute_value); > > Cert Attributes don't matter at my setups -- the complete table is empty. > For what is it used anyway within other implementations? If you use subject alternative names or forced validity, this info is recorded here as a 1:n relation. Oli -- Protect your environment - close windows and adopt a penguin! PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
