4 ms·
>PG can't roll back, because he isn't using a database backend. I was afraid of that... May I ask why? Too much resource usage? Arc doesn't have a DB API?
by unimpressive 15y ago
>PG can't roll back, because he isn't using a database backend.
I was afraid of that...
May I ask why? Too much resource usage? Arc doesn't have a DB API?
- Estragon 15y agoWho cares, really? It's all play money.
- unimpressive 15y agoWell of course. I don't really care about the Karma. If I got spammed to death I'd just make a new account. I was just wondering because it seems like an odd design decision. I wanted to know the rationale behind it.
- abtinf 15y agoVia email, I asked PG about this 7 years ago. me: "I've read in your essays that you (and yahoo) chose to store all your information in files rather than a database. I am curious if you would make the same decision now that excellent oss databases are available (mysql, postgresql, etc)." PG: "I'd do the same thing. It was a huge win to use alists (a lisp construct) and just write them to files. Then if anything went wrong, or data formats changed, I could just munge the raw files. Nothing was wired in."
- unimpressive 15y agoThank you for answering. At the same time however, I'm not really sure what to think about that. On the one hand future proof is a massive win. On the other no rollbacks seems like a risky way to operate. I hope he keeps regular backups of the data files.