My favorite lines:
"theres not much code since its all done online"
"no der is not FTP setup for the database"
Enjoy: http://www.phpfreaks.com/forums/index.php/topic,123774.0.html
My favorite lines:
"theres not much code since its all done online"
"no der is not FTP setup for the database"
Enjoy: http://www.phpfreaks.com/forums/index.php/topic,123774.0.html
[quote user="dArkPL"]
If some company would treat users like that, I would never use their services...
[/quote]
Luckily for them, they have more users. Seriously, it's not going to kill digg if you complain. It's not going to kill them if that domain can't register, obviously the benefits of blocking that domain outweigh the loss of users.
[quote user="dArkPL"]
And show me, where I've been rude in my correspondence with Digg Support.
[/quote]
Demanding: "I will not accept simple explanation, I want to know exact reason, why my >domain is blocked and cannot be used."
"I dont like to be forced to do things that I dont want to do
" - well, duh, who does?
The real wtf (OMG HAHA!) is Digg Support's grammar. "Please trying"
... you have an excuse, but Digg is an English site.
[quote user="dArkPL"]Geez. Then it would be nice if they would explain me, why this domain is blocked, rather than saying something about TOS violations, Im not an idiot, that will accept any crap that they will tell me.
[/quote]
They DID explain to you why it was blocked - because of TOS violations from that domain. Just because you demand to know more doesn't mean they have to tell you - for all they know, you're one of the violators, and you did come off as very rude. If someone wrote to me like that, I'd simply hit delete and be glad they didn't join my site. Digg has enough users without you...
[quote user="merreborn"]
[quote user="PlasmaHH"]I get 10 of those every month. The real WTF here is that someone took the time to replace all the email addresses and hosts...[/quote]
I usually respond quickly with a snopes link and a rather blunt 'don't spread misinformation' email. Last time I did that, the original sender promptly sent an apology with said snopes link to everyone he'd forwarded the chain letter to.
[/quote]
I did that to my grandma once. Then I felt bad :(
She stopped sending me forwards though.
I work for a company which, among other things, publishes an online daily newsletter. They hired an 'editor' who doesn't know wtf he's doing, and he hired a bunch of other writers.
Again, this is an ONLINE publication.
Most of these writers handwrite their articles and mail them to the editor, who then types them and posts them on the site under their accounts, because these individuals are "not willing to post online, or type".
*headdesk*
[quote user="Brendan Kidwell"]
We have those in CVS drugstores in New England. I've asked the checkout clerks about them--how can they tolerate it? why don't they do something about it? The clerks just shrug their shoulders and say they don't notice it.
I've been meaning to write a letter to the chain, complaining about it. It's EXTREMELY annoying to me as a customer, and it's really encouraging me not to come back to the store.
[/quote]
I feel the same way about the new Techron speaking gas pump thing. It starts playing annoying music as you pump and tells you about all the points you can earn
[quote user="lpope187"]
Okay I gotcha now - It was the end of the day and I wanted to go home. Offhand, I can't think of a way to remove the duplicates in one shot. What I'd do is create a temporary table and select the unique records into it. Then you delete the contents of the original and then reinsert the contents from the temp table back into the original.
So you would have something along the lines of the following.
Insert Into Temp_MyTable (ID, Name) Select ID, Name From MyTable Group By ID, Name
Delete From MyTable
Insert Into MyTable (ID, Name) Select ID, Name From Temp_MyTable Order By ID
If you need it done in one shot so that the database is still usable while your working on it, you could wrap the statements in a transaction so that all the modifications are committed at the same time.
[/quote]
That makes sense, thanks :)
I fixed the table and the code - but I wanted to remove all the duplicates in one query.
How does a select remove the extras?
I have a postgresql database which got triplicates of its entries. (That part is fixed)
So now I have
id | name
1 | bob
1 | bob
1 | bob
2 | jane
2 | jane
2 | jane
Can I remove the two extras and leave the one for the whole set of 400+?
Thanks :)