3 ms·
I'm not saying the performance isn't important in this case, I'm saying it's an inherently unsafe implementation. I can't think of a single way to secure the sy
by gravypod 10y ago
I'm not saying the performance isn't important in this case, I'm saying it's an inherently unsafe implementation. I can't think of a single way to secure the system if the password falls to the wrong hands.
I'd much rather have this done in a query language and have the queries cached. A compiled query should be very small (maybe only a few instructions) and if done right could be very quick without any fancy meta evaluation. You'd also get "some" way to sandbox the system inherently.
The code should only be able to access your data and if you design a language around that idea your have something infinitely more safe then something that isn't.