DDC-1433: Sf doesn't warn if I set a variable in Entity not connected to DB in ORM #1796

Closed
opened 2026-01-22 13:26:14 +01:00 by admin · 2 comments
Owner

Originally created by @doctrinebot on GitHub (Oct 18, 2011).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user r1pp3rj4ck:

I merged two branches and apparently I failed to resolve a conflict, so the 'deleted' field vanished from the ORM, but still was in Entity and the generated schema. So when I deleted an object (set deleted to 1), nothing happened. Shouldn't the Doctrine at least warn in dev environment that it's an invalid field?

Originally created by @doctrinebot on GitHub (Oct 18, 2011). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user r1pp3rj4ck: I merged two branches and apparently I failed to resolve a conflict, so the 'deleted' field vanished from the ORM, but still was in Entity and the generated schema. So when I deleted an object (set deleted to 1), nothing happened. Shouldn't the Doctrine at least warn in dev environment that it's an invalid field?
admin added the Bug label 2026-01-22 13:26:14 +01:00
admin closed this issue 2026-01-22 13:26:14 +01:00
Author
Owner

@doctrinebot commented on GitHub (Oct 31, 2011):

Comment created by @beberlei:

Transient fields (non-mapped) are perfectly valid

@doctrinebot commented on GitHub (Oct 31, 2011): Comment created by @beberlei: Transient fields (non-mapped) are perfectly valid
Author
Owner

@doctrinebot commented on GitHub (Oct 31, 2011):

Issue was closed with resolution "Invalid"

@doctrinebot commented on GitHub (Oct 31, 2011): Issue was closed with resolution "Invalid"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#1796