![[The AI Show Episode 151]: Anthropic CEO: AI Will Destroy 50% of Entry-Level Jobs, Veo 3’s Scary Lifelike Videos, Meta Aims to Fully Automate Ads & Perplexity’s Burning Cash](https://www.marketingaiinstitute.com/hubfs/ep%20151%20cover.png)
_Andrea_Danti_Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
![Google Pixel 10 series launch date might actually be August 20 [Update]](https://i0.wp.com/9to5google.com/wp-content/uploads/sites/4/2024/09/Pixel-9-Pro-XL-camera-bar-low-light.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1){kind=tracking}
![Apple AI Launch in China Delayed Amid Approval Roadblocks and Trade Tensions [Report]](https://www.iclarified.com/images/news/97500/97500/97500-640.jpg)
Best practice for ORM design (re: cascading delete from single entity)
If I have a very common shared table (ie. names) with a primary key (ie. name_id) included in many other tables as foreign keys, do I need my common table (names) to have a mapping reference to every other foreign key table for cascade deletes to work? For example: Name myName = session.Get(12345); session.Delete(myName); However, name_id is referenced in many other tables. If I want cascade delete, then my Name class needs to have references to every other table and every other table has a reference back to Name. Is this correct or are there any other approaches? It seems like a violation of separation of duties (?) for my Name class to be aware of other classes that refer to it.
If I have a very common shared table (ie. names) with a primary key (ie. name_id) included in many other tables as foreign keys, do I need my common table (names) to have a mapping reference to every other foreign key table for cascade deletes to work?
For example:
Name myName = session.Get(12345);
session.Delete(myName);
However, name_id is referenced in many other tables. If I want cascade delete, then my Name class needs to have references to every other table and every other table has a reference back to Name.
Is this correct or are there any other approaches?
It seems like a violation of separation of duties (?) for my Name class to be aware of other classes that refer to it.
