DDC-259: Generated SQL should end with a ';' #319

Closed
opened 2026-01-22 12:34:33 +01:00 by admin · 2 comments
Owner

Originally created by @doctrinebot on GitHub (Jan 16, 2010).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user shurakai:

Currently, if one generates the SQL from the metadata and asks the doctrine CLI to output it, the statements are not separated by ';'.

Therefore, one can not simply use copy & paste (okay, one could leave the --dump-sql option out, but thats not the point) but needs to include the ';' sign after each statement. This would be really cool, but I'm not sure whether one would have to extend every Platform by a method "getStatementTerminationSign()" or something like that.

What do you think?

Originally created by @doctrinebot on GitHub (Jan 16, 2010). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user shurakai: Currently, if one generates the SQL from the metadata and asks the doctrine CLI to output it, the statements are not separated by ';'. Therefore, one can not simply use copy & paste (okay, one could leave the --dump-sql option out, but thats not the point) but needs to include the ';' sign after each statement. This would be really cool, but I'm not sure whether one would have to extend every Platform by a method "getStatementTerminationSign()" or something like that. What do you think?
admin added the Improvement label 2026-01-22 12:34:34 +01:00
admin closed this issue 2026-01-22 12:34:34 +01:00
Author
Owner

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

Comment created by @beberlei:

Implemented

@doctrinebot commented on GitHub (Feb 2, 2010): Comment created by @beberlei: Implemented
Author
Owner

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

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Feb 2, 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#319