>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2702495. --> Reported by: [plopesc](https://www.drupal.org/user/282415) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We have a project were we make use of <a href="https://www.drupal.org/project/domain">Domain Access</a> and <a href="https://www.drupal.org/project/domain_entity">Domain Entity</a> modules to give access beans only in specific domains.</p> <p>Everything worked fine, but when the number of beans has increased, we noticed an error when creating new ones.<br> <code>PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'test' for key 'delta': INSERT INTO {bean} (vid, delta, label, title, type, view_mode, data, uid, created, changed) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8, :db_insert_placeholder_9); Array ( [:db_insert_placeholder_0] =&gt; 0 [:db_insert_placeholder_1] =&gt; test [:db_insert_placeholder_2] =&gt; Test [:db_insert_placeholder_3] =&gt; Test [:db_insert_placeholder_4] =&gt; inspirations_introduction [:db_insert_placeholder_5] =&gt; default [:db_insert_placeholder_6] =&gt; a:1:{s:9:"view_mode";s:7:"default";} [:db_insert_placeholder_7] =&gt; 331 [:db_insert_placeholder_8] =&gt; 1460042381 [:db_insert_placeholder_9] =&gt; 1460042381 ) in drupal_write_record() (line 7334 of /my/path/www/includes/common.inc).</code></p> <p>Then we realized that Bean module was not able to detect we already had a bean with delta <code>test</code> and renamed our new bean to <code>test-0</code>. We realized there was a conflict between Bean &amp; Domain entity module because original "test" bean was not visible in the domain we were creating the new "test" bean.</p> <p>After some debug we discover that problem was in <code>bean_load_delta()</code> function, which is called from <code>Bean::checkDelta()</code> method. This function does 2 things:</p> <ol> <li>Check against the Database if already exists beans with a certain delta</li> <li>Load those beans and return them</li> </ol> <p>First step is completely OK and the query return the already existing Bean ID. So things are good so far. However, when trying to load the entity, Domain entity module alters the load entity query to hide beans not available for the current domain, so instead of returning the entity, it returns <code>FALSE</code>.</p> <p>Given that step 1 works as expected, and we don't really need in <code>Bean::checkDelta()</code> the loaded entity, we propose to create a new method in Bean class <code>Bean::deltaExists()</code> where we just make the first query against the DB to ensure if already exists a bean using that delta.</p> <p>Besides of that, this would increase performance because we would skip an unnecessary call to <code>bean_load()</code> function.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Get rid of <code>bean_load_delta()</code> call in Bean class</li> <li>Create a specific method in the class </li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li><del>Create patch</del></li> <li>Review</li> <li>Commit patch</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None</p> <h3 id="summary-api-changes">API changes</h3> <p>None</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>We would add a new method in <code>Bean</code> class decoupling it from <code>bean.module</code> file and increasing performance.</p>