Option to ignore Association alias 'Foobar' is already set errors while baking

[nook24]

Description

Hi,
this issue is a follow up of #1059. Currently it is not possible to ignore any Association is already set errors when baking models. In my case I have a Systems table with an system_id. The baking logic is creating an association to itself, which results into the error message.

Steps to reproduce:

bin/cake bake migration CreateSystems system_id:string  created modified
bin/cake migrations migrate

bin/cake bake all systems

I think it is Ok to print this out as a warning. How ever in my case system_id is not a foreign key, it's an ID provided by another system. My workaround for this was, to temporarily rename the column.

mysql> alter table `systems` rename column `system_id` to `herbert_id`;

mysql> \! bin/cake bake all systems

mysql> alter table `systems` rename column `herbert_id` to `system_id`;

While this is maybe an edge case, I think we should keep the power by the developer. If bake detects something sketchy, print a warning. That's fine. The CakeException should only be thrown at runtime.

Error:

/var/www/html # bin/cake bake all systems
Bake All
-------------------------------------------------------------------------------
One moment while associations are detected.
2026-06-15 10:06:54 error: [Cake\Core\Exception\CakeException] Association alias `Systems` is already set. in /var/www/html/vendor/cakephp/cakephp/src/ORM/AssociationCollection.php on line 84
Stack Trace:
- CORE/src/ORM/AssociationCollection.php:110
- CORE/src/ORM/Table.php:1140
- ROOT/vendor/cakephp/bake/src/Command/ModelCommand.php:281
- ROOT/vendor/cakephp/bake/src/Command/ModelCommand.php:163
- ROOT/vendor/cakephp/bake/src/Command/ModelCommand.php:115
- ROOT/vendor/cakephp/bake/src/Command/ModelCommand.php:97
- ROOT/vendor/cakephp/bake/src/Command/AllCommand.php:120
- CORE/src/Console/BaseCommand.php:258
- CORE/src/Console/CommandRunner.php:375
- CORE/src/Console/CommandRunner.php:193
- ROOT/bin/cake.php:10
- [main]:

CakePHP version: 5.3.6

[LordSimal]

The error happens in CakePHP, not in bake, as we prevent users from adding/overwriting an already existing association like so

$this->belongsTo('MyName');
// other code
$this->hasMany('MyName');

Since we dynamically create a table instance with its associations in bake based on the schema, this can of course happen like you explained above.

And your schema has a systems table with a system_id column - so based on our naming conventions we generate both a hasMany Systems and a belongsTo Systems association - which collides from a naming perspective.

---

You also mentioned in slack, that this system_id is not really a internal ID referencing other tables but a external ID. I'd rather recommend you rename your column to system like system_ident or anything else other than a XYZ_id column as we use that name in CakePHP for detecting associations between tables.

We should not fix this as imho this is not a bug in CakePHP.

[dereuromark]

I opened a PR that addresses this 2nd dimension here. The other one was already addressed with PR to #1059

But since the primary issue was already addressed before, this "de-duping" is indeed not too relevant anymore.

[ADmad]

We should look into preventing bake from creating such self associations, since generally for self associations the fK field used is parent_id.

[nook24]

Thanks for your quick response. I leave it up to you if you consider this as a valid bug report or not. In this case, the column is named system_id across different platforms. To keep my ecosystem as consistent as possible I cannot change the name.

The reason I opened this issue is, because I stumbled across this issue twice now :)

[dereuromark]

#1094