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

Fix support of different engines #94

Closed
Jeckerson opened this issue May 31, 2020 · 0 comments · Fixed by #98
Closed

Fix support of different engines #94

Jeckerson opened this issue May 31, 2020 · 0 comments · Fixed by #98
Assignees
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@Jeckerson
Copy link
Member

Currently, it is not possible to create table with different engines, for example: MEMORY.

@Jeckerson Jeckerson self-assigned this May 31, 2020
@Jeckerson Jeckerson added bug Something isn't working enhancement New feature or request labels May 31, 2020
@Jeckerson Jeckerson added this to the 2.2.x milestone Aug 31, 2020
@Jeckerson Jeckerson added this to Working on it in Phalcon Roadmap Aug 31, 2020
@Jeckerson Jeckerson modified the milestones: 2.2.x, 2.1.x Aug 31, 2020
@Jeckerson Jeckerson changed the title Add support of different engines Fix support of different engines Aug 31, 2020
Jeckerson added a commit that referenced this issue Aug 31, 2020
Jeckerson added a commit that referenced this issue Aug 31, 2020
@Jeckerson Jeckerson linked a pull request Aug 31, 2020 that will close this issue
Phalcon Roadmap automation moved this from Working on it to Implemented Aug 31, 2020
Jeckerson added a commit that referenced this issue Aug 31, 2020
#94 - Fixed engine and another table options declaration
@niden niden moved this from Implemented to Released in Phalcon Roadmap Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Archived in project
Phalcon Roadmap
  
Released
Development

Successfully merging a pull request may close this issue.

1 participant