Upgrade Database Errors
Permalink
I have a client who used a different table type and when I brought the computer to my local server with the usual setup for Concrete5, I got this error:
An Unexpected Error occurred while upgrading: mysql error: [1210: Incorrect arguments to DATA DIRECTORY] in EXECUTE("ALTER TABLE btFormAnswerSet MODIFY COLUMN asID INTEGER UNSIGNED NOT NULL AUTO_INCREMENT")
I was told by the client's tech support that I have to change the table structure from innodb to myisam. But, I don't know what that means.
I am not allowed to work on their server so I have to do the work locally on my computer and convert the sql file table so not to get these errors. Any SQL experts who can guide me?
An Unexpected Error occurred while upgrading: mysql error: [1210: Incorrect arguments to DATA DIRECTORY] in EXECUTE("ALTER TABLE btFormAnswerSet MODIFY COLUMN asID INTEGER UNSIGNED NOT NULL AUTO_INCREMENT")
I was told by the client's tech support that I have to change the table structure from innodb to myisam. But, I don't know what that means.
I am not allowed to work on their server so I have to do the work locally on my computer and convert the sql file table so not to get these errors. Any SQL experts who can guide me?
mhawke, I would have the IT person at the University convert it back. Work flow for this University client is 10% dodging red tape. As an outsider I can see this process would not make sense to you, but the reason is because they do not let freelancers work on their University servers. And, if the site crashes from what I did, no one gets upset because the individuals I work with know my handicap because of the red tape, and the IT patches up my work when I return the job to him. The servers at this university come bare, so I need help from the IT guy at the beginning of the job and during upgrades.
I understand completely Stephen. My brother is the HR webmaster at a very large university and it took them almost 2 years to decide to switch all their departmental websites over to Joomla only to have huge security issues and abandoned the rollout. It took them another year to decide to use Cascade and another year to move content over. He hates Cascade but after 4 years he's happy to have anything working at all!
Good luck with the red tape!
Good luck with the red tape!
So you do understand, everything moves verrry slowwww at large universities and there are a lot of hoops to jump through. But, at least the people I work with are really nice and are always happy with what I give them.
And their cheques rarely bounce!
I know lots of developers build on a local system but I refuse to do that. I have to make sure everything works on their server and I don't like looking silly when it crashes on their real server during a demo. I'd rather have it crash during the first week of development and fix all the issues then. Also, I want to make sure the speed is acceptable and when I develop on localhost, I never get a sense of what my client is going to face when they start working with the system.
just my 2 cents.