(no subject)

[techieb0y.livejournal.com]

After much back-and-fourthing with a vendor, we have determined that:

1. The program crashed because the database was corrupt.
2. The database corrupted because the program crashed.

*headdesk*

Comments

[gotica.livejournal.com]

Those two things sound mutually exlusive.

[coyoteden.livejournal.com]

Yup. Can and does happen. Database apps develop eating disorders.

They can get anorexic and refuse everything you feed them.
Or they can get bulimic and gobble up massive amounts of memory right before they BARF ALL OVER EVERYTHING.

Still can't beat the users who generate an ssh keypair, send me the public key, then ask me what the private key's passphrase is...

[jon787.livejournal.com]

Yossarian approves this problem.

[the-s-guy.livejournal.com]

There's a hole in that bucket.

[10001110101.livejournal.com]

Solution:

1. Place database, program, and all other associated servers in a sealed box with a certain Austrian physicist's cat.

2. Whatever you do, don't look in the box

3. ???

4. PROFIT!

[doublefelix.livejournal.com]

Ah, the age old question: Which came first, the program crash or the database corruption?

[brotherflounder]

Whichever isn't your fault.

[kizayaen.livejournal.com]

That could be a disastrous math error. A negative TIMES a negative is a positive. A negative PLUS a negative is a bigger negative and just makes it even more your fault.

[mashiroikaze.livejournal.com]

Quick - someone call the guys at CERN and tell them that at some point in the future, they're going to do something that fucks up causality on database servers everywhere.

Seriously - wtf. Causality loops suck.