Problem connecting to existing PartKeepr database - unknown database type enum requested

[Gasman2014]

I have a working Partkeepr 1.1.0 installation. I have now managed to upgrade to 1.2 and have confirmed basic functionality incl Octopart integration - the reason for the upgrade.

I have followed the instructions for copying my data/ directory and parameters.php file over from the 1.1 to the 1.2 install. I have then run setup again. If I then select the MySql database of parts from my 1.1 install, it connects but then I get the following error whilst 'setting up database schema'

Apparently this is a recognised error as discussed here https://wildlyinaccurate.com/doctrine-2-resolving-unknown-database-type-enum-requested/ with a suggested solution.

I do not have the skills to implement this in your code myself so would appreciate any advice!

[Drachenkaetzchen]

PartKeepr doesn't use ENUM, so this error is very strange. Do you probably have other software installed in the same database?

For further analysis, I'd need a database dump which contains the database structure only. You can create one either by using mysqldump -d <databasename> -u <yourusername> -p or use phpMyAdmin to export all tables without the data.

[Gasman2014]

It was some Pma_#### tables from phpMyadmin that were causing the problem. Now just need to figure out how to get rid of them.

John

Felicia Hummel notifications@github.com wrote:

PartKeepr doesn't use ENUM, so this error is very strange. Do you probably have other software installed in the same database?

For further analysis, I'd need a database dump which contains the database structure only. You can create one either by using mysqldump -d -u -p or use phpMyAdmin to export all tables without the data.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/partkeepr/PartKeepr","title":"partkeepr/PartKeepr","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/partkeepr/PartKeepr"}},"updates":{"snippets":[{"icon":"PERSON","message":"@felicitus in #807: PartKeepr doesn't use ENUM, so this error is very strange. Do you probably have other software installed in the same database?\r\n\r\nFor further analysis, I'd need a database dump which contains the database structure only. You can create one either by using mysqldump -d \u003cdatabasename\u003e -u \u003cyourusername\u003e -p or use phpMyAdmin to export all tables without the data.\r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/partkeepr/PartKeepr/issues/807#issuecomment-276939208"}}}

[Gasman2014]

Errant 'PMA' tables had been created in the database from phpMyAdmin. When removed, database imported without issue and now working fine.