@Kemp said:
My first thought was that the crazy red blob was giving the first kid a vasectomy.
Cutting off a child's head is some kind of delayed vasectomy, in a way.
O_o
@Kemp said:
My first thought was that the crazy red blob was giving the first kid a vasectomy.
Cutting off a child's head is some kind of delayed vasectomy, in a way.
O_o
plesk works as long as you do no nothing special with it and never ever try to remove anything ( customers, domains, web user, whatever ).
last one for me was plesk taking down subdomains, but never enabling them back up, if the 'suspend domaine during backup' option was on in the backup manager.
subdomains remained in an unstable state, with no way to restore them (unless you go sql within the plesk database).
@clively said:
So, here's a question for the people here: Do systems you work with/on store credit card details? If so, why? I have yet to see anyone with a valid reason for it.
i do work with paiement processing systems for several clients, one of them cashes in > 5 millions € every year.
we never ever store credit card numbers, it's useless, and retarded.
yes we do things like giving people their money back, or recurring paiements (you're given an unique combo of references for future uses, depending on your banking partners), you just don't need to keep the card numbers, no fucking point.
an old doctype should be enough to return to the old behavior. no ?
@Shinhan7 said:
I'll assume the original code is PHP. I'll rewrite it to use variable variables :)
for ($i = 1; $i < 6; $i++) {
$entity->{'setNickname'.$i}($nicknames['nickname' . $i]);
}
that's not ugly enough, future proof version !
$i=1; while (method_exists($entity,"setNickname$i")) $entity -> {"setNickname$i"}($nicknames['nickname' . $i++]);
@blakeyrat said:
Or waiting for someone else (usually me) to post a topic even slightly remotely related to the topic they were too cowardly to post, then hijacking my post with it. If that sentence makes sense, it made sense in my head.
ITT : blakeyrat hijacking a vaguely related rant-about-coworker topic so he can rant again about his weird obsession of hijacked topics.
pure trolling genius.
as it's case insensitive, maybe the 'do not use symbols' is only there to lower the number of troubleshooting/support calls from confused users with caps-lock on.
@shimon said:
Me, I don't remember this happening in my lifetime. Success stories, anyone?
I did it, but always on my own initiative because fuck this shit i won't work with such code knowing i can fix it in a reasonnable amount of time, and in a small pirate ship kind of company.
as soon as any kind of management is involved, no, refactoring never happens.
@PJH said:
. and it's not innodb.
true, and he is probably using innodb, that would explain the 'slow'' truncate as well.
maybe you could do a show tables, then select count(*) from each one (instant answer as long as you have a pk), put that data aside then mysdump one table at at time and show the user "processed tables X/Y, processed records W/Z, currently dumping table table_name ( table_name_count records )"
on a funny side note, the first patch for the game broke anything magic-resistance-related.
Beth then said that the next patch will be carefully crafted not to break anything.
Then the second patch send to oblivion (huhu) all non us/ascii caracters in localised versions ot the game.
Bethesda.