Add a DB::execute($query) to execute unprepared queries #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some DMBS DDL statements needs to be run unprepared, as shown in this issue: #53.
Creating test for proposed execute() method.
|
Implemented as DB::unprepared. Thanks. |
|
Very helpful here! |
This was referenced Dec 7, 2016
|
But then some complex queries involving temporary tables and other will not work with any of the DB raw methods but works fine in console even with unprepared, other than just returning bool |
joelharkes
pushed a commit
to joelharkes/framework_old
that referenced
this pull request
Mar 7, 2019
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some DMBS DDL statements (like CREATE TRIGGER in MySQL) needs to be run unprepared, as shown in issue #53.