Changes between Version 1 and Version 2 of CryptoPlugin/Dev/DbSchema
- Timestamp:
- Jun 25, 2012, 7:57:43 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CryptoPlugin/Dev/DbSchema
v1 v2 5 5 6 6 == Common "parasite" storage == 7 Entries in `session_attribute` seem like a perfect match for the first requirement. 7 Session attributes are easily accessible related on a client sessions base in Trac's Request object (`req.session`), without the need for a direct db connection. 8 So entries in Trac db table `session_attribute` seem like a perfect match for the first requirement - no need for an own db table here. 8 9 I've chosen the following dedicated names for related association types: 9 10 * 'sign_key' 10 11 * 'crypt_key' 11 12 * 'auth_key' (''future'') 13 Their meaning should be easily guessable from these names. 12 14 13 15 == Dedicated "private" storage == … … 22 24 * version, 23 25 * fragment, 24 i* key_id,26 i * key_id, 25 27 signature 26 itime,28 i time, 27 29 28 * primary key 29 i has dedicated index: 30 Legend: 31 * primary key 32 i has dedicated index 30 33 }}} 31 34