# Parent/Child Relationship **URL:** \ **Category:** Ask for Help\ **Created:** [April 16, 2024, 7:39pm UTC](https://community.glideapps.com/t/parent-child-relationship/72633 "2024-04-16T19:39:06Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [April 18, 2024, 1:12pm UTC](https://community.glideapps.com/t/parent-child-relationship/72633/6 "2024-04-18T13:12:45Z")
It depends. Glide does not do atomic operations, so if it is essential that you should never have duplicates, then you should use the solution shown in the video. Otherwise, see below: > [@How do I create an auto-incrementing row number with Glide Tables?](https://community.glideapps.com/t/how-do-i-create-an-auto-incrementing-row-number-with-glide-tables/39572): > > This is a question that comes up a lot, so creating this topic to use as a reference. Typically, there are two distinct use cases when it comes to auto-incrementing row numbers. Use Case 1: – We need to generate a Part Number, or an Order Number, or an Employee ID. Once the number is generated, it should never change, even if rows are deleted. – The general approach for this use case is to maintain a static counter, use it to craft a suitably formatted ID, and increment it by one every time… --- _[View the full topic](https://community.glideapps.com/t/parent-child-relationship/72633)._