Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] 3.0.x #131

Open
wants to merge 40 commits into
base: 2.0.x
Choose a base branch
from
Open

[WIP] 3.0.x #131

wants to merge 40 commits into from

Conversation

Fenikkusu
Copy link

Hello!

  • Type: bug fix
  • Link to issue: N/A

In raising this pull request, I confirm the following (please check boxes):

  • [*] I have read and understood the Contributing Guidelines
  • [*] I have checked that another pull request for this purpose does not exist
  • I wrote some tests for this PR

Small description of change:

Updating Migration To Be Phalcon 5.0.x Compatible

NOTE: Currently Targeting 2.0.z, but a new 3.0.x branch should probably made for this as Phalcon 5.0.x is not backwards compatible with 4.0.x

Thanks

Ultimater and others added 30 commits August 3, 2021 14:35
* ISSUE-112: Fixed empty index type on pgsql adapter usage

* ISSUE-111: Replaced pgsql unsupported double type to supported float

* Codestyle fixes

* Added tests and validation fixes

* PHP 8 support

* updating tests and lock file

* .

* test ci adjustments

* adjusting tests phalcon 5 installation

* adjusting tests

* updated composer packages

* replaced deprecated assert

* disabled psalm negative rule

* CHANGELOG

* ISSUE-111: Column types fix

* ISSUE-112: mkdir redundant call removed

* typehints on db testers seeExceptionThrown

Co-authored-by: Kevin Yarmak <[email protected]>
# Conflicts:
#	CHANGELOG.md
#	composer.json
#	composer.lock
#	src/Migrations.php
#	src/Mvc/Model/Migration.php
…n-morph-table

ISSUE-97: Renaming column does not drops column on morphTable
@Jeckerson
Copy link
Member

This is good PR, but I think we need to break it in smaller parts, as there are a lot of changes, that are not even might related to v5 compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants