storing keyrings into SQL database?

[David Picon Alvarez]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> It does not make much sense.  keyrings are internal to gpg and their
> internals may change without notice.  Also an SQL DB is far too slow
> for gpg's purposes - frankly, the current code to handle keyrings is
> too slow.

Somewhat off-topic, but is this slowness accidental or essential? Is it
likely to go away in the future?

- --David.

-----BEGIN PGP SIGNATURE-----
Comment: This message is digitally signed and can be verified for authenticity.

iQIVAwUBPsjqu6YOp7uFKb/EAQK40A/+LHK1GkQw4cibOnw9I5LJXbaqQNIzUTAO
oodnQdlADMpwmS4vtb2JDtewkdLrm9UtG1IPXVrdYd828qgC1fCOdwkEaI25+smk
lsgc5DXPMwQg7TUDSgrChNPPaBxP5Q2f5I8QBfK0SrvQwdMTVFVC9yxuc14LDKLr
dBxxDZGBrP2QtOH+vTQYceE/v9q1G/MHbaHBnYsEApgRzMMesNwC75qLtRn0zHXR
RfIGEFjS++bZVUjJikcPxFczqryRjPb9jYl+F6GiLNpUI2egdZ1grs2YaZoPoG/O
zQyprr1GNLaMrJNHDQfliaSW/lkEeQcWIvBBOOKPpPnOiwJ67qROeJ0JYB6Dz9tS
udHPKIyeQKPukEFtZmusspr1CmGq3Mgz1Z6huoi/CxsAwsprR2HEqzORN+JjFy3l
YU1Xn5p7H7mpU5Lcs50g0zU93luKYJDliMXHBoBlj1hgrQOLZEniYqe9d1W6UQmE
2FSRKctBLVqYjNSriiY3XE+XtjpYUPI9ModFGDMdnVWifpy7ufdKacHKjP6nfwOv
wD/1to6NhFRZAEHFx+08rwEI/KpBoeqmBaiFj8p58cxCoTAPo2x+lQuOeBhhX5SF
26rRERY2Xe+StBMluuPuaMo4D6yl0KzxsWODyP4xAglDLlaMmGFW6xlw/8oCWVB9
EMJlzcZELRI=
=JtJp
-----END PGP SIGNATURE-----