-
Notifications
You must be signed in to change notification settings - Fork 24
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
Initialize.sql fails - table doesn't support fulltext indexes for MySQL 5.5 and below #4
Comments
Context- I'm attempting to build from the Digital Ocean LAMP 14.04 Droplet. MySQL Version: 5.5.46-0ubuntu0.14.04.2 |
Stackoverflow seems to suggest an upgrade of MySQL or changing the engine to MyISAM: http://stackoverflow.com/questions/20964269/1214-the-used-table-type-doesnt-support-fulltext-indexes |
It looks like there's some MySQL 5.6 stuff in here. Maybe the README requirements should be updated. |
I'd be willing to bet just removing the I made the switch to InnoDB for version 2 for data integrity reasons, and there's still future work to do to allow Silex to leverage that capability fully. EDIT: If you remove the FULLTEXT index from the Initialize script, and this then fixes the initialize script, feel free to open another PR with this fix (and reference this issue). Thanks! |
Fair enough. I'll take another look at it to see if I can cobble together a script that works. I've been considering deployment to a couple different places in the cloud, including OpenShift, and all of those places seem to default to MySQL 5.5 as the de-facto starting environment. I'll try to remove the fulltext indexes and see if I can get everything to build. Since the the original attempt was on a DigitalOcean instance, I just nuked it from orbit when it didn't work, since those instances aren't free. I'll try this again on OpenShift and see if that makes anything easier. |
I'd certainly be open to relaxing some database constraints in order to satisfy requirements for one minor version number lower of MySQL. When writing the docs I didn't think I had used anything crazy new for 5.6 (I think PHP Draft 1.3 ran fine on 5.3 and 5.4 but thats just a hunch), but 5.5 is not much older and shouldn't drastically change things much, so I'd be open to making it work for a platform like OpenShift. |
Had a few minutes to look at this and there are a few other instances of breaking changes between 5.5 and 5.6 that I did not account for (other than the FULLTEXT instances). I'll take a look at it when I have more time and will try to patch this up so it can be run on an OpenShift instance - as I'd like to do the same myself. |
Sweet. It's good to hear that we're have the same outlook on that. |
@zo0o0ot so I just worked through the issues I had to get PHPDraft up and running on OpenShift. Since it's cloud-based, it's insanely fast (10x faster than my shared hosting, no surprise there). I'm going to eventually add another markdown file detailing instructions on how to install the app on OpenShift, because it's pretty easy. Here's what I found:
The last one was a pain (thanks to http://stackoverflow.com/a/14921890/324527 for saving my sanity ), and I had to commit to delete the "submodule" first, then run the Composer install and re-commit the entire directory. I'll be pushing these changes up as part of 2.0.1, but you're probably savvy enough to get it up and running. |
I fixed Initialize.sql as well as a few minor fixes elsewhere in 2.0.1, and also added an install guide specific to OpenShift as I think this is a perfect solution for folks who want to run their own installs. Refer to OPENSHIFT_DEPLOYMENT.md for details, and let me know if you have any issues! |
I think this is awesome. Technically, it could be possible to streamline the setup even more, but I'm not certain if it's worth the trouble. I found openshift through an pretty snazzy auto-deploying Bolt CMS instance. https://github.com/Atriedes/openshift-boltcms-quickstart It's possible that this project may be able to borrow from that in order to streamline the process, but as long as I can get phpdraft on openshift and running, you won't be hearing any complaints from me. I have a mandrill account set up for a different purpose, so I might end up using them for email delivery. If any directions need updating, I'll let you know. I might also use MySQL Workbench instead of phpMyAdmin. I was able to get that going through ssh by checking a couple different setup parameters in the MySQL Workbench local client, and I can share those setup instructions with an update of the Openshift deploy docs if I get things up and working. I'm probably going to give it a whirl tonight. |
script fails at this query:
Response:
"Error Code: 1214. The used table type doesn't support FULLTEXT indexes"
The text was updated successfully, but these errors were encountered: