Is there a need to specify many to many relation instead of one to many if we are using only either side to fetch the data?
For example, if products and categories is a many to many relation, but what if we are only fetching the products with the specific categories, not fetching the categories with the products associated with them.
Is there a need to specify many to many relation instead of one to many if we are using only either side to fetch the data?
For example, if products and categories is a many to many relation, but what if we are only fetching the products with the specific categories, not fetching the categories with the products associated with them.
Is there a need to specify many to many relation instead of one to many if we are using only either side to fetch the data?
For example, if products and categories is a many to many relation, but what if we are only fetching the products with the specific categories, not fetching the categories with the products associated with them.
Is there a need to specify many to many relation instead of one to many if we are using only either side to fetch the data?
For example, if products and categories is a many to many relation, but what if we are only fetching the products with the specific categories, not fetching the categories with the products associated with them.
update duplicate rows based on latest date in postgres database
My requirement is to keep the latest vin and reject the duplicate vin by updating the error_status as ‘y’.