DDC-313: Remove all the unnecessary stuff from Schema and Platform, like Triggers #390

Closed
opened 2026-01-22 12:36:49 +01:00 by admin · 4 comments
Owner

Originally created by @doctrinebot on GitHub (Feb 10, 2010).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user @beberlei:

-There should be graceful support for triggers in DBAL\Table instances if this is possible accross platforms.-

-Relevant use-cases are a post schema generation event in SchemaTool or any application that works with triggers. Some databases might even require Trigger support to allow for foreign key or auto-increment keys like Sqlite (FK) or Oracle (Auto-Increment). This could then nicely be done by the Fix Schema visitor which transforms "explicit" database objects into the database supported object that emulates this behaviour.-

There is so much dead and unnecessary code in DBAL\Platform and DBAL\Schema that should be removed.

Originally created by @doctrinebot on GitHub (Feb 10, 2010). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user @beberlei: -There should be graceful support for triggers in DBAL\Table instances if this is possible accross platforms.- -Relevant use-cases are a post schema generation event in SchemaTool or any application that works with triggers. Some databases might even require Trigger support to allow for foreign key or auto-increment keys like Sqlite (FK) or Oracle (Auto-Increment). This could then nicely be done by the Fix Schema visitor which transforms "explicit" database objects into the database supported object that emulates this behaviour.- There is so much dead and unnecessary code in DBAL\Platform and DBAL\Schema that should be removed.
admin added the Improvement label 2026-01-22 12:36:49 +01:00
admin closed this issue 2026-01-22 12:36:49 +01:00
Author
Owner

@doctrinebot commented on GitHub (Feb 11, 2010):

Comment created by @beberlei:

The following information is required to completely define a trigger, any platform that does not support the creating and retrieval of this information returns false on "supportsTriggers".

  • Trigger-Name
  • Trigger Action Event - One of "INSERT", "UPDATE", "DELETE"
  • Trigger Timing "BEFORE", "AFTER"
  • Trigger Command: The code to be executed

All 4 platforms Mysql, Sqlite, Oracle and Postgres support retrieval and adding of this information.

@doctrinebot commented on GitHub (Feb 11, 2010): Comment created by @beberlei: The following information is required to completely define a trigger, any platform that does not support the creating and retrieval of this information returns false on "supportsTriggers". - Trigger-Name - Trigger Action Event - One of "INSERT", "UPDATE", "DELETE" - Trigger Timing "BEFORE", "AFTER" - Trigger Command: The code to be executed All 4 platforms Mysql, Sqlite, Oracle and Postgres support retrieval and adding of this information.
Author
Owner

@doctrinebot commented on GitHub (Feb 11, 2010):

Comment created by @beberlei:

Not possible in a general way, additionally list functions and list users are quite useless also. Will all be removed.

@doctrinebot commented on GitHub (Feb 11, 2010): Comment created by @beberlei: Not possible in a general way, additionally list functions and list users are quite useless also. Will all be removed.
Author
Owner

@doctrinebot commented on GitHub (Feb 11, 2010):

Comment created by @beberlei:

Removed a great bunch of unnecessary and un-needed code from Platform and Schema.

@doctrinebot commented on GitHub (Feb 11, 2010): Comment created by @beberlei: Removed a great bunch of unnecessary and un-needed code from Platform and Schema.
Author
Owner

@doctrinebot commented on GitHub (Feb 11, 2010):

Issue was closed with resolution "Fixed"

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

No dependencies set.

Reference: doctrine/archived-orm#390