Twitter | Pretraživanje | |
Rob Stradling 7. lip 2017.
Odgovor korisniku/ci @sbutterworth
LOL! I reserve the right to not answer questions that are out of scope. ;-)
Reply Retweet Označi sa "sviđa mi se"
Rob Stradling 7. lip 2017.
Odgovor korisniku/ci @comfreak @ivanristic
$1 is a placeholder. Try changing $1 to (for example) ''.
Reply Retweet Označi sa "sviđa mi se"
Rob Stradling 7. lip 2017.
Odgovor korisniku/ci @comfreak @ivanristic
From that error message, I'm guessing that your SQL client is automatically appending a LIMIT clause to the query. Try trimming the ";".
Reply Retweet Označi sa "sviđa mi se"
BenBE 7. lip 2017.
Odgovor korisniku/ci @Cryptoki
Ist the SQL schema available/documented somewhere? Are there tables for the plain SPKI?
Reply Retweet Označi sa "sviđa mi se"
Rob Stradling 8. lip 2017.
Odgovor korisniku/ci @BenBE1987 @Cryptoki
Schema created by . There's no SPKI table, but the "certificate" and "ca" tables have indexes relating to SPKI.
Reply Retweet Označi sa "sviđa mi se"
Julien Vehent 12. lip 2017.
Odgovor korisniku/ci @clintw_
I've been wanting to provide SQL access to TLS Observatory for a while. How did you build it? A dedicated read-only slave? Any rate limits?
Reply Retweet Označi sa "sviđa mi se"
Rob Stradling 13. lip 2017.
Odgovor korisniku/ci @jvehent @clintw_
Yes, some dedicated read-only slaves. No rate limits yet (and we'll just have to see how that goes... ;-) ).
Reply Retweet Označi sa "sviđa mi se"