You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Codecs may unlock the ability for us to put custom translations in to convert to/from what's in the database. An interesting use case for this might be a feistel cipher - you could tag a particular tables primary key as @feistel and then whenever it's used (even in foreign key relations) it could be automatically converted to a random-looking number on the way out, and converted back to the underlying number away on the way back in. If we've coded everything that use these values (Node IDs, cursors, etc) to use the codecs then this should be possible... I think. It'll be a fun experiment if so!
Codecs may unlock the ability for us to put custom translations in to convert to/from what's in the database. An interesting use case for this might be a feistel cipher - you could tag a particular tables primary key as
@feistel
and then whenever it's used (even in foreign key relations) it could be automatically converted to a random-looking number on the way out, and converted back to the underlying number away on the way back in. If we've coded everything that use these values (Node IDs, cursors, etc) to use the codecs then this should be possible... I think. It'll be a fun experiment if so!https://en.wikipedia.org/wiki/Feistel_cipher
The text was updated successfully, but these errors were encountered: