Slashdot videos: Now with more Slashdot!
2016 Election: Cruz vs. Clinton -- You'll vote Clinton.
Just like you would if it was Rand Paul, Marco Rubio, Scott Walker, Rick Perry, Jeb Bush...
You'll vote for Clinton, and happily remind yourself she'd be Obama's third term -- only a bigger disaster than Obama's been.
Vince Foster's death
Ron Brown's death
Rose Law Firm
The alleged rape of Juanita Brodderick
The Paula Jones Sexual Harassment Lawsuit
Bill Clinton lying under oath, aka PERJURY about his relationship with Monica Lewinsky
"It depends what your definition of the word 'is' is"
Missile strikes on an aspirin factory in the Sudan
Removing 'W' from White House keyboards
My God, people... the Clinton administration was the most corrupt in history, and we want to go BACK to that?
Bullshit. You'll vote for her.
Now THAT's the funniest thing I've ever read on Slashdot.
Please google the following: Rose Law Firm, Whitewater, Vince Foster, Benghazi, Travelgate, Troopergate, the Vast Right Wing Conspiracy...
Hitlary Clinton is as corrupt and fascist as they come.
ABP works so well that I didn't realise for quite a while that they'd introduced advert videos until I went round a friend's house.
The people agitating the most for socialism will be the first to die of hunger.
The attack on Christianity is no accident.
I believe there was 1 -- Joseph Cao of Louisiana, who (i think) promptly got himself thrown out of office next election.
* googles * YES! I remembered right.
That is silly. A falling bullet has a much lower speed than one that was just shot. I've been hit by shotgun pellets at the end of their range, it was like having gravel slung at you.
A returning bullet CAN hit someone, and possibly injure them if everything is lined up right, or there is a very low angle of fire, but they have a small fraction of the energy they had in the first km after being fired.
More aggressive than SJW's, even.
(SJW = SOCIAL JUSTICE WARRIOR, SERIOUS YOU GUYS!!!)
How do OIDs solve this? Updating a record it still updating a record. OIDs don't magically make that problem go away.
One solves this problem the way one solves any other data problem: logical thinking and planning ahead. If you are creating a long-running business application where things like addresses may change, you design your database to take that into account. You store a timestamped address with every order record, or you store multiple addresses by date range. It's not exactly rocket science.
There is literally no reason to use OIDs except as a crutch when one has created a table without a primary or candidate key--and even then OIDs won't save you from bad logic, such as duplicate records or other idiocy.
BTW, it is important to also remember that OIDs are not enabled by default for new table creation. Many times the PostgreSQL core team has discussed whether to deprecate OIDs completely. The decision was made to keep them for two reasons: a) some applications still depend on them, however misguided their reasons and b) Some PostgreSQL add-ons and external solutions (replication, etc...) use them.