cubicweb #1381382 regression: supressing a non committed relation in the web interface fails [resolved]
Steps to reproduce:
Bug : both relations have been committed. I cannot reproduce this on an instance running 3.9.9, but instances running 3.10.5 have this behavior (could not test with earlier 3.10.x versions) | |
priority | important |
---|---|
type | bug |
done in | 3.10.7 |
load | 0.500 |
load left | 0.000 |
closed by | <not specified> |
similar entities
- cubicweb-forge #1399287 Change the standard validation process of the tickets
- cubicweb #901407 support for backup/restore of bfss
- cubicweb #1806898 ical view: UID is not unique across generations of the view
- cubicweb #344897 wrong ticket creation date in project principal view
- cubicweb #197665 locking strategies for concurrent edition
[see all]
Comments
-
2010/11/18 22:00, written by sthenault
-
2010/11/24 09:55
-
2010/12/01 15:36, written by sthenault
-
2010/12/01 15:49, written by sthenault
-
2010/12/02 07:39
-
2010/12/02 07:40
-
2010/12/02 09:16, written by sthenault
-
2010/12/02 14:38
- the schema defines A rel B and A can be related to 0 or 1 B
- I edit a B entity, change some attribute values, browse for an A entity to be linked with my B entity, select an A entity
- I realize that I selected the wrong A entity, so I click on the "X" to cancel that association
- at that point I decide to Apply the changes : the relation with the A entity is established. If that entity was previously related to another B entity, that relation is lost, and I have to easy way to restore it.
-
2010/12/02 18:06, written by sthenault
-
2010/12/03 07:36
add commenttied to 3.10 jQuery version update?
This is a very baaaaad bug because on some relation with a 1 cardinality, a previously linked entity will no longer be linked, causing corruption of the DB.
could you detail this?
which entity has the 1 cardinality ? the edited entity or the target entity ?
can I reproduce it on a forge instance ?
huum, I can't reproduce the described pb (eg without talking about unrespected cardinality).
The thing is that, as I expected, when I remove a not yet commited relation, the link is not striked but disappear totally. And then everything seems ok to me.
I've just reproduced this issue on this very ticket, with two "identical to" relations although one had been deleted before I clicked on Validate.
I'll be happy to discuss this with you over the phone, if you think it will help.
ok, I've reproduced this one and pushed a fix in stable branch. Still fail to see the potential db corruption pb though.
Can you check the fix and mark this ticket as done if it's enough?
thx
the db corruption pb occurs in the following case:
ok. So we agree that:
* it's not db corruption in the sense of non respected constraint causing integrity error
* we may consider everything is fine once the described bug is fixed
Have you tried the fix ?
no, it is db corruption in the sense that I asked something, got something else and can't revert the change.
didn't get a chance to reproduce (my instances are running 3.9), will try today.