dubswithus

Joined 4 years ago

Karma

688

Submissions

424

Member since

Apr 16

View on Hacker News

Recent submissions

Comment · 4 years ago

Imagine someone offered you a house but the agreement was that you could only sell it for what you bought it for. I doubt you would buy it considering there are other options on the market where you could profit in the future. It's 100% speculation. It's part of the package.

Comment · 4 years ago

When are you going to ban this user? Their username is sexual and offends me as a woman.

https://news.ycombinator.com/user?id=MegaButts

Comment · 4 years ago

Link should be changed.

Comment · 4 years ago

You bought it to live in for 5 years and then you flipped it for more money than you bought it? That's the definition of successful speculation.

Comment · 4 years ago

All homeowners are real estate speculators.

Wouldn't you also consider anyone buying a "starter home" a speculator? Their goal is to continuously flip their house.

Comment · 4 years ago

Very good points MegaButts. Crypto is VC funded too. Hence the crazy market caps because most of the VC owned supply is locked up.

Comment · 4 years ago

The business owns your data. Why would they delete it if they don't have to?

Comment · 4 years ago

There's definitely perfect and perfect for the business. But when large companies have many developers they all have to do something. They will spend their time doing something unnecessary.

Comment · 4 years ago

I would never suggest archiving unless we're hitting some performance limit. Why generate more busy work? Just leave it there and if need be add more indexes and partitions.

Comment · 4 years ago

The use case for using the database here is overblown. I've never experienced of heard of anyone using a view for the users table. I suppose it may exist in the wild somewhere.

I wouldn't avoid Ruby features because the applications I develop are in Ruby and it would require a complete rewrite anyway. I avoid the database because there are development speed advantages to using Rails features. And everything works together nicely assuming you do things the Rails way.

https://github.com/rubysherpas/paranoia

> If a record has has_many associations defined AND those associations have dependent: :destroy set on them, then they will also be soft-deleted if acts_as_paranoid is set, otherwise the normal destroy will be called.

It's convenient.

Comment · 4 years ago

There are Rails gems that can handle this in various ways.

But the easiest way is to deactivate the user account (is_active boolean) and continue to reference the user in internal records.

Comment · 4 years ago

There are some Rails gems that take care of this by scoping associations (that also have the deleted_at column).