DDC-1212: Exception of mapping of ID generation strategy #1521

New Issue

admin · 2026-01-22T13:16:53+01:00

admin commented

2026-01-22 13:16:53 +01:00

Originally created by @doctrinebot on GitHub (Jun 16, 2011).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user comfortablynumb:

Hi all,

After updating today Doctrine 2 from master branch I'm getting:

Entity of type "Entity" is missing an assigned ID. The identifier generation strategy for this entity requires the ID field to be populated before EntityManager#persist() is called. If you want automatically generated identifiers instead you need to adjust the metadata mapping accordingly.

Was there a change on the mapping of ID generation strategy? I was using a commit of the master branch from 1 o 2 weeks ago and it was working ok. I took a look at the repo for changes on the last days but I couldn't find anything related to this.

I paste the mapping and entities here:

Element:

/****
 * @ORM\MappedSuperclass
 */
abstract class Element
{
    /****
     * @ORM\Id
     * @ORM\Column(type="integer")
     * @ORM\GeneratedValue(strategy="IDENTITY")
     */
    protected $id;
}

File:

/****
 * @ORM\Entity
 * @ORM\Table(name="file")
 * @ORM\InheritanceType("JOINED")
 * @ORM\DiscriminatorColumn(name="discriminator", type="string")
 * @ORM\DiscriminatorMap({
        "image"  = "Image",
    })
 */
abstract class File extends Element
{
     // Fields
}

And Image:

/****
 * @ORM\Entity
 * @ORM\Table(name="image")
 */
class Image extends File
{
     // Fields
}

Thanks in advance!

Originally created by @doctrinebot on GitHub (Jun 16, 2011). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user comfortablynumb: Hi all, After updating today Doctrine 2 from master branch I'm getting: Entity of type "Entity" is missing an assigned ID. The identifier generation strategy for this entity requires the ID field to be populated before EntityManager#persist() is called. If you want automatically generated identifiers instead you need to adjust the metadata mapping accordingly. Was there a change on the mapping of ID generation strategy? I was using a commit of the master branch from 1 o 2 weeks ago and it was working ok. I took a look at the repo for changes on the last days but I couldn't find anything related to this. I paste the mapping and entities here: Element: ``` /**** * @ORM\MappedSuperclass */ abstract class Element { /**** * @ORM\Id * @ORM\Column(type="integer") * @ORM\GeneratedValue(strategy="IDENTITY") */ protected $id; } ``` File: ``` /**** * @ORM\Entity * @ORM\Table(name="file") * @ORM\InheritanceType("JOINED") * @ORM\DiscriminatorColumn(name="discriminator", type="string") * @ORM\DiscriminatorMap({ "image" = "Image", }) */ abstract class File extends Element { // Fields } ``` And Image: ``` /**** * @ORM\Entity * @ORM\Table(name="image") */ class Image extends File { // Fields } ``` Thanks in advance!

admin added the Bug label 2026-01-22 13:16:53 +01:00

admin referenced this issue

2026-01-22 14:24:25 +01:00

DDC-2922: Flushing new Entities reachable over several paths that do not all "cascade persist" #3637

admin referenced this issue

2026-01-22 15:00:32 +01:00

Wrong ORMInvalidArgumentException "A new entity was found through the relationship ..." #5171

admin referenced this issue

2026-01-22 16:04:45 +01:00

[PR #1521] [DDC-2922] Error when new entities are reachable through multiple paths but not all of them are marked cascade-persist #9580

Sign in to join this conversation.