Matthew Peveler
Matthew Peveler
Can you open a new bug report with a migration that demonstrates that bug?
How about something like this for an API: ```php /** * @param string $viewName the name for the view * @param string $viewQuery the query to use for the view...
Having a wrapper would not prevent you from writing the raw SQL instead, same as the `$this->table` construct? Unless this is a broader commentary that phinx should just rip out...
Could you provide a migration that demonstrates the bug?
Could you provide an example migration?
As you note this is not supported in phinx currently, and your current option would be to do a direct `$this->execute("ALTER TABLE tag_data DROP PRIMARY KEY, ADD COLUMN td_id int(11)...
@othercorey can you re-open this? This is something I've wanted in Phinx for a while, as having to do combinations of grep, head, tail, etc. is not the most friendly...
Yes, though I will probably make a new issue that combines this one and #1506, as the geometry handling in phinx needs quite a bit of work that should probably...
How are you connecting to the database that is causing the throw to have a non-number `code`? ~Per the [PHP docs for PDOException](https://www.php.net/manual/en/class.pdoexception.php), `code` should always be an `int`.~. Nevermind,...
Thanks for the information. I've opened a PR to just not bother setting the code for the recasted exception, and hopefully downstream users of phinx are not relying on that...