Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Way of matching user form #339

Open
rolintoucour opened this issue Jun 10, 2015 · 0 comments
Open

Way of matching user form #339

rolintoucour opened this issue Jun 10, 2015 · 0 comments

Comments

@rolintoucour
Copy link

Submitting a form that is a collection of elements, the match between the type data and the user data is based on the index of the elements.

In a concurrent edition of a form, it may cause troubles, eg:

  • two users open the same form of a collection of 3 elements,
  • the first user adds an element and save => successfull,
  • the seconds also adds an element => the form handling process matches its fourth element to the first user's added element, instead of detecting it is a new element. Moreover, as no PK has been sent by the second user, his element will be associated to the PK of the first user's element, this PK will be marked as a 'modified column' and propel will try to set the PK and will crash at saving.

The match seems to be based on the element index, instead of the primary key.

@havvg havvg added the Bug label Jan 22, 2016
@havvg havvg added this to the 1.5 - Symfony 2.8 LTS support milestone Jan 22, 2016
@havvg havvg added the Forms label Jan 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants