--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org
iROD-Chat: http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/irod-chat/77734db7-aae2-4acf-8c23-caefcaa97614n%40googlegroups.com.
1. This is then what I would expect
2. This is why I ask questions, because my thinking in irods didn't go this far yet and I am very glad yours is. Your table row 7 clearly shows what I cannot imagine any irods user would want to happen typically. However, it is in principle a valid usecase, when you made a wrong update on a replica and want to rollback.
3. It could be a no-op without error, as the replica is there in the resource you want, but replicating a file or a collection to the same resource it came from doesn't really seem to make sense anyway. In automation however you might want to have no error, but also there it should be an easily preventable edgecase.