Using cobalt types as reviews may cause website issue

Fixed.

Sergey Fixed.

Are they deleted? Or do you keep the related records?

Maybe both solutions can be necessary and should be considered?!

Hello pepperstreet

I dont see why would you want to keep a comment/review on your website for something which does not exists anymore on the website, that may be confusing and useless I`d say.

Rgds

jimie I dont see why would you want to keep a comment/review on your website for something which does not exists anymore on the website, that may be confusing and useless I`d say.

maybe in your case it makes no sense. I can emagine there are many other usecases for related child/parent records. If someone (user, moderator) is able to delete the parent... this might happen on purpose or even accidently... Then the related data would be lost immediately, too. No way to restore and repair anything. Also, there might be multiple parents and child connections! Example: A related movie directory like IMDB.com Deleting a movie, would remove all actors.

In this case here we are talking of using "Cobalt - Types as comments" in a type "Comments parameters" and not a parent and chield, but anyway I`ll let Sergey check your opinion :)

Rgds

jimie In this case here we are talking of using "Cobalt - Types as comments" in a type "Comments parameters" and not a parent and chield,

Ooops, yes. Slightly different topic and use case ;)

However, sitebuilders might use the "Cobalt type as Comments" feature in another context and application. i.e. Attend an event; Job board and applicants; etc.

Anyway, it might come in handy to keep the "attached records".

pepperstreet Are they deleted? Or do you keep the related records?

I delete them.

pepperstreet many other usecases for related child/parent records

It is not a related child/parent issue. It is cobalt type as comment. This is different.

pepperstreet Anyway, it might come in handy to keep the "attached records".

May be yes, but it contains link to non existing article which make no sense for article which is supposed to be only related record like review. If theer is no product anymore, you cannot keep review.

To me it absolutely make sense to delete those articles.

There is only one reason to let them stay - audit trail. When we delete with ability to restore. After restore those articles will be lost now. But since article snapshot is a very complex thing, it will be not easy to slove this problem. So it will work like this for now.

I am just curious and want to know, what if comment type has its own child field ? for exmaple : if type " Review " has its own child field ( attachable by user )

ron.du I am just curious and want to know, what if comment type has its own child field ? for exmaple : if type " Review " has its own child field ( attachable by user )

No problems. There is not limitation on relations depth and amount.