-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Magento 2.0.x and 2.1.x does not respect table prefix during installation #5688
Labels
bug report
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Comments
At least someone to confirm this issue?! |
Thanks @andimov ! |
Hi @stamster Thanks for reporting it! Thanks, |
mmansoor-magento
pushed a commit
that referenced
this issue
Sep 13, 2016
…e prefix during installation #5688
The issue has been resolved. |
@katmoon You're welcome, I'm glad that it is fixed. |
okorshenko
pushed a commit
that referenced
this issue
Dec 14, 2016
… respect table prefix during installation #5688 - for 2.0
okorshenko
pushed a commit
that referenced
this issue
Dec 14, 2016
… respect table prefix during installation #5688 - for 2.1
slavvka
pushed a commit
that referenced
this issue
May 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug report
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Steps to reproduce
Expected result
Installation finished w/o any errors.
Actual result
Installation is incomplete.
Check the console log for errors before trying again
Magento fails with [ERROR] exception 'PDOException'!
So Magento fails here big time with NOT respecting table prefix entered during installation, instead it CHECKS for actual data from old installation with DIFFERENT table prefix?! It even checks entire database for each table like
admin_user
table which does not have any prefix and complains that email is already taken etc if you really don't have any table prefix.TABLES CREATED DURING INSTALLATION:
van_cache
,van_cache_tag
,van_flag
,van_session
,van_setup_module
,van_store_website
and after this it just fails.How in the world this is possible, or is it a new requirement for M2 to have empty database, i.e. table prefixes are not supported any more?
This is issue is present from v.2.0.4+ as I experienced it multiple times.
Here's a full stack trace.
The text was updated successfully, but these errors were encountered: