3 ms·

> so their customers get distracted from the fact that they are paying $500+ per user per month for a shitty web UI on top of 4 database tables. Oof, I felt th

> so their customers get distracted from the fact that they are paying $500+ per user per month for a shitty web UI on top of 4 database tables. Oof, I felt that cut in my bones and I was only a customer.

lazide 2y ago
slow database tables too.
- rawgabbit 2y ago
  A minor nitpick. SF doesn’t have tables. It is not a relational database. It is slow because it is an enterprise application. The link details the steps that are triggered every time a record is updated. https://www.salesforceben.com/learn-salesforce-order-of-execution/ https://www.salesforceben.com/learn-salesforce-order-of-exec...
  - layman51 2y ago
    Salesforce’s product is technically is a relational database. Maybe it doesn’t perfectly fit the relational model that Edgar Codd theorized, but I don’t think any widely used database product does. A crucial aspect of the relational database is that the tables have columns which refer to another table (e.g. AccountId) and this what they call “lookup relationships” or “master-detail relationships” in Salesforce. Also, I recently learned that SQL has triggers too in case you want the same procedure to take place after an INSERT, UPDATE, etc.
    - rawgabbit 2y ago
      In Salesforce everything is an API call with hard limits eg you can only return 200 records unless you hit the bulk api. JOINS do not exist in Salesforce. Instead you have to create bridge tables. Even then you can only traverse a max of three objects at a time. Please do not try to use Salesforce as a general database, you are only putting yourself in a world of hurt.