Martin Bartosch wrote:
- introduce a new table, e. g. CA Purpose: - identification and reference of CA certificate for internal CAs - mapping between internal and external CAs Attributes: INTERNAL_CA: internal CA EXTERNAL_CA: external CA this CA belongs to CA_CERT_SERIAL: serial number of the CA certificate (foreign key to the CERTIFICATE table)No comments on this? I think this is the most important change, the other stuff is more or less cleanup and avoidance of redundancy.there is, of course, an argument against this and explicitly in favour of including EXTERNAL_CA *and* INTERNAL_CA in each data object: If you change the association of EXTERNAL_CA and INTERNAL_CA in the table above, all previously created entries are changed implicitly. Of course, this association *should* never be changed, an INTERNAL_CA is not supposed to be "changing" to another EXTERNAL_CA. If we keep the relation in all the individual database entries, we have "historical" information about the association as it was when the item was created, but we also keep a lot of redundancy that could bite some time in the future.
Do you really want to change such an association? This is for me a no-no. Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
