Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Hell No Hillary (Score 1) 676

by RailGunner (#49462759) Attached to: Hillary Clinton Declares 2016 Democratic Presidential Bid
Clintons had far more than 2 scandals. Look, I realize you were probably in diapers during the Clinton administration, so please google the following:
Vince Foster's death
Ron Brown's death
Rose Law Firm
Troopergate
Travelgate
Whitewater
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?

Comment: Re:Time to stock up on shotgun shells (Score 2) 162

by Pharmboy (#49361329) Attached to: How long until our skies are filled with drones?

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.

Comment: Re:Postgres has referential integrity (Score 1) 320

by rycamor (#49298847) Attached to: Why I Choose PostgreSQL Over MySQL/MariaDB

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.

Theory is gray, but the golden tree of life is green. -- Goethe

Working...