sferik/rails_admin — pull request #1736 by davidgoli (2013-09-05 18:34:44+00:00)
Title: no reason to explicitly assign an id to a new object

We found a bug when creating new records via the "new" form. Objects were not able to be saved because the id was already in the database. There's no need in Rails to explicitly set an id on create, and since it causes bugs, is there any reason not to remove it?