I guess, you can query your data's history like how Wikipedia did. And you could revert it.

I am using Seaweedfs with 40+ TB data and ~100M files. Serve 100-200k+ users daily with servers that just have HDD.

I have 30T+ data and ~100M files to serve 100k+ users daily.

Two years ago, I tried Minio, but its performance (small files) was very bad in comparison with Seaweedfs. However, you should benchmark it again now, as it may have improved.

Also, our servers only use HDDs.

I think people who lack understanding about the internet may prioritize privacy because they don't truly comprehend it. Please correct it if I'm wrong.

It is not always bad to harvest data. As a developer, I understand that there are often valid reasons for doing so.

I'm not sure where everyone got the idea that tracking and harvesting data is always bad.

In addition, it is essentially impossible to have something harmful happen to you if you refrain from entering your bank password on websites.

Harvesting data is almost always bad

There are a tiny handful of use cases where it is not

I don't understand how people are not more aware of the invasiveness of such activities

In the past, I used adblock, but now I only allow it on 1% of websites. It's only necessary for 1% of websites.

The reason is that I now have a website and earn money through ad banners, so I understand how challenging it is to optimize ad banners. Meanwhile, we may have 60% of users using adblock in certain fields.

I am using Prisma in the production. I want to ask:

- Can EdgeDB solve the problems like `soft-delete`? Prisma can't do this good, there are third-party packages, but I don't trust these packages because authors often drop support.

- How about hooks, for example, I want to trigger scripts after/before a record is added to the table.

> Can EdgeDB solve the problems like `soft-delete`?

Yes, with access policy rules. E.g

   global hide_deleted: bool;

   type SoftDeletable {
     deleted: bool;

     access policy hide_deleted
       allow all
       when (global hide_deleted)
       using (not .deleted);
   }

The above will effectively "hide" objects with `.deleted` set to `true` from all queries when the `hide_deleted` global is set to true.

> How about hooks, for example, I want to trigger scripts after/before a record is added to the table.

EdgeDB supports triggers: https://www.edgedb.com/docs/changelog/3_x#triggers. Future versions will add support for causing effects outside of the database, e.g. call a WebHook or some such.

I think the main reason: the forum is expensive. They cost a big chunk of money to set up for a large community.

And they missed so many features like a mobile app and notifications. And a lot of things that Discord offered.

Is there a database that supported arrays of foreign keys?

Of the major databases, only Oracle and PostgreSQL have array extensions and neither support FKs as array elements.

I'm curious how people think this feature should work? ON DELETE SET NULL, ON DELETE CASCADE, something else?

I would love it if the would remove the key from the array.

We use it in Palantir, that is a proprietary overlay on top of Spark. It supports this feature reasonably fine.

I think no one has the answer to your question. Everyone doesn't really know your team's personality and how many people agree/happy with his decision.

How about we vote on this?