News for hackers. Stuff that matters.
Re:Salesforce will hire no more software engineers in 2025, ... by rawgabbit on Wednesday January 08, 2025 @11:25PM (#42641617)
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-exec...

Re:Salesforce will hire no more software engineers in 2025, ... by layman51 on Friday January 10, 2025 @02:12PM (#42658941)
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.

Re:Salesforce will hire no more software engineers in 2025, ... by rawgabbit on Sunday January 12, 2025 @02:02PM (#42675898)
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.