-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Error happenes when installation #30
Comments
You can't use the current sample data with Magento 2. |
Right. Magento 1.x database dumps are incompatible with Magento 2.x. The problem is in backwards-incompatible changes done on DB level so far. Due to elimination of "factory names" of classes and tables, there are backwards-incompatible changes in values of some columns, which were storing these names. Specifically, fields in
... or Thus, a value that used to be
We plan to have sample data as a module, rather than a DB dump. Originally it was brought by an old community issue http://www.magentocommerce.com/bug-tracking/issue?issue=8061 Currently intentions are to separate any sample content (CMS pages, blocks, banners) into a module, then to implement ability to choose to disable this module during installation. These changes most likely will be implemented at some point before GA release of Magento 2.0 Although this comment provides our best view of the product direction, priorities can change and features may be adjusted. As a result, we do not recommend making firm business decisions solely based on the information above. Attempting to repair a 1.x DB dump would be a very hard manual operation, but theoretically it is possible, provided that you have all formal backwards-incompatible changes documented. These changes are constantly being recorded to developer's guide as we go and perform backwards-incompatible changes. |
…e-theme-version [Extensibility] MAGETWO-25343: Declaration of Components: XML VS composer.json - Removed version from theme.xml
First I create database in mysql, then I import the data of magento_sample_data_for_1.6.1.0.sql. When I install the magento2, there are a lot same errores. In page, the following error:
Zend_Db_Statement_Exception Object
(
[_previous:Zend_Exception:private] =>
[message:protected] => SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento2.customer/eav_attribute' doesn't exist
[string:Exception:private] =>
[code:protected] => 42
[file:protected] => D:\xampp\htdocs\magento2\lib\Zend\Db\Statement\Pdo.php
[line:protected] => 234
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => D:\xampp\htdocs\magento2\lib\Varien\Db\Statement\Pdo\Mysql.php
[line] => 110
[function] => _execute
[class] => Zend_Db_Statement_Pdo
[type] => ->
[args] => Array
(
[0] => Array
(
[:id] => disable_auto_group_change
[:entity_type_id] => 1
)
INNER JOIN
customer/eav_attribute
ASadditional
ON main.attribute_id = additional.attribute_id WHERE (main.attribute_code = :id) AND (main.entity_type_id = :entity_type_id)[1] => Array
(
[:id] => disable_auto_group_change
[:entity_type_id] => 1
)
INNER JOIN
customer/eav_attribute
ASadditional
ON main.attribute_id = additional.attribute_id WHERE (main.attribute_code = :id) AND (main.entity_type_id = :entity_type_id)[1] => Array
(
[:id] => disable_auto_group_change
[:entity_type_id] => 1
)
INNER JOIN
customer/eav_attribute
ASadditional
ON main.attribute_id = additional.attribute_id WHERE (main.attribute_code = :id) AND (main.entity_type_id = :entity_type_id)[1] => Array
(
[:id] => disable_auto_group_change
[:entity_type_id] => 1
)
INNER JOIN
customer/eav_attribute
ASadditional
ON main.attribute_id = additional.attribute_id WHERE (main.attribute_code = :id) AND (main.entity_type_id = :entity_type_id)[1] => Array
(
[:id] => disable_auto_group_change
[:entity_type_id] => 1
)
The text was updated successfully, but these errors were encountered: