Call-back icon  Sales: Call 877.832.5289 (N America)|310.295.4144 (International)

Magento

eCommerce Software for Online Growth

419 users online   

Magento Forum

   
DB tables differ among ver.1 and 1.0.19870.4 ! 
 
nabuhonodozor
Member
 
Avatar
Total Posts:  38
Joined:  2008-03-27
 

Hi,
After troughly compare databases structure between Magento Ver.1 (release 1) and 1.0.19870.4 I can say ther differ!

Following by “--->” are differencess (first part for DB Ver. 1.0.19870.4, second, after “=====..” for DB Ver.1) :

FOR Table: core_config_data

CREATE TABLE IF NOT EXISTS `core_config_data` (
  `config_id` int(10) unsigned NOT NULL auto_increment,
  `scope` enum('default','websites','stores','config') NOT NULL default 'default',
  `scope_id` int(11) NOT NULL default '0',
  `path` varchar(255) NOT NULL default 'general',
  `value` text NOT NULL,
--->`old_value` text NOT NULL,
---> `inherit` tinyint(4) NOT NULL default '0',
  PRIMARY KEY  (`config_id`),
  UNIQUE KEY `config_scope` (`scope`,`scope_id`,`path`)
) 

======================
CREATE TABLE IF NOT EXISTS `core_config_data` (
  `config_id` int(10) unsigned NOT NULL auto_increment,
  `scope` enum('default','websites','stores','config') NOT NULL default 'default',
  `scope_id` int(11) NOT NULL default '0',
  `path` varchar(255) NOT NULL default 'general',
  `value` text NOT NULL,
  PRIMARY KEY  (`config_id`),
  UNIQUE KEY `config_scope` (`scope`,`scope_id`,`path`)
)

FOR TABLE: eav_attribute

CREATE TABLE IF NOT EXISTS `eav_attribute` (
  `attribute_id` smallint(5) unsigned NOT NULL auto_increment,
  `entity_type_id` smallint(5) unsigned NOT NULL default '0',
  `attribute_code` varchar(255) NOT NULL default '',
  `attribute_model` varchar(255) default NULL,
  `backend_model` varchar(255) default NULL,
  `backend_type` enum('static','datetime','decimal','int','text','varchar') NOT NULL default 'static',
  `backend_table` varchar(255) default NULL,
  `frontend_model` varchar(255) default NULL,
  `frontend_input` varchar(50) default NULL,
  `frontend_label` varchar(255) default NULL,
  `frontend_class` varchar(255) default NULL,
  `source_model` varchar(255) default NULL,
  `is_global` tinyint(1) unsigned NOT NULL default '1',
  `is_visible` tinyint(1) unsigned NOT NULL default '1',
  `is_required` tinyint(1) unsigned NOT NULL default '0',
  `is_user_defined` tinyint(1) unsigned NOT NULL default '0',
  `default_value` text,
  `is_searchable` tinyint(1) unsigned NOT NULL default '0',
  `is_filterable` tinyint(1) unsigned NOT NULL default '0',
  `is_comparable` tinyint(1) unsigned NOT NULL default '0',
  `is_visible_on_front` tinyint(1) unsigned NOT NULL default '0',
  `is_unique` tinyint(1) unsigned NOT NULL default '0',
--->`is_visible_in_advanced_search` tinyint(1) unsigned NOT NULL default '0',
  `is_configurable` tinyint(1) unsigned NOT NULL default '1',
  `apply_to` varchar(255) NOT NULL default '',
  `position` int(11) NOT NULL default '0',
  `note` varchar(255) NOT NULL default '',
  PRIMARY KEY  (`attribute_id`),
  UNIQUE KEY `entity_type_id` (`entity_type_id`,`attribute_code`)
) 
===========

CREATE TABLE IF NOT EXISTS `eav_attribute` (
  `attribute_id` smallint(5) unsigned NOT NULL auto_increment,
  `entity_type_id` smallint(5) unsigned NOT NULL default '0',
  `attribute_code` varchar(255) NOT NULL default '',
  `attribute_model` varchar(255) default NULL,
  `backend_model` varchar(255) default NULL,
  `backend_type` enum('static','datetime','decimal','int','text','varchar') NOT NULL default 'static',
  `backend_table` varchar(255) default NULL,
  `frontend_model` varchar(255) default NULL,
  `frontend_input` varchar(50) default NULL,
  `frontend_label` varchar(255) default NULL,
  `frontend_class` varchar(255) default NULL,
  `source_model` varchar(255) default NULL,
  `is_global` tinyint(1) unsigned NOT NULL default '1',
  `is_visible` tinyint(1) unsigned NOT NULL default '1',
  `is_required` tinyint(1) unsigned NOT NULL default '0',
  `is_user_defined` tinyint(1) unsigned NOT NULL default '0',
  `default_value` text,
  `is_searchable` tinyint(1) unsigned NOT NULL default '0',
  `is_filterable` tinyint(1) unsigned NOT NULL default '0',
  `is_comparable` tinyint(1) unsigned NOT NULL default '0',
  `is_visible_on_front` tinyint(1) unsigned NOT NULL default '0',
  `is_unique` tinyint(1) unsigned NOT NULL default '0',
  `is_configurable` tinyint(1) unsigned NOT NULL default '1',
  `apply_to` varchar(255) NOT NULL default '',
  `position` int(11) NOT NULL default '0',
  `note` varchar(255) NOT NULL default '',
--->`is_visible_in_advanced_search` tinyint(1) unsigned NOT NULL default '0',
  PRIMARY KEY  (`attribute_id`),
  UNIQUE KEY `entity_type_id` (`entity_type_id`,`attribute_code`)
)

FOR TABLE: product_alert_stock

KEY `FK_PRODUCT_ALERT_PRICE_CUSTOMER` (`customer_id`),
  
KEY `FK_PRODUCT_ALERT_PRICE_PRODUCT` (`product_id`),
  
KEY `FK_PRODUCT_ALERT_PRICE_WEBSITE` (`website_id`)
============
KEY `FK_PRODUCT_ALERT_STOCK_CUSTOMER` (`customer_id`),
  
KEY `FK_PRODUCT_ALERT_STOCK_PRODUCT` (`product_id`),
  
KEY `FK_PRODUCT_ALERT_STOCK_WEBSITE` (`website_id`)

FOR TABLE: tax_rate_data

CREATE TABLE IF NOT EXISTS `tax_rate_data` (
  `tax_rate_data_id` int(10) unsigned NOT NULL auto_increment,
  `tax_rate_id` int(10) unsigned NOT NULL default '0',
  `rate_value` decimal(12,4) NOT NULL default '0.0000',
  `rate_type_id` tinyint(4) NOT NULL default '0',
  PRIMARY KEY  (`tax_rate_data_id`),
  KEY `rate_id` (`tax_rate_id`),
  KEY `rate_type_id` (`rate_type_id`)
) 
===========
CREATE TABLE IF NOT EXISTS `tax_rate_data` (
  `tax_rate_data_id` int(10) unsigned NOT NULL auto_increment,
  `tax_rate_id` int(10) unsigned NOT NULL default '0',
  `rate_value` decimal(12,4) NOT NULL default '0.0000',
  `rate_type_id` tinyint(4) NOT NULL default '0',
  PRIMARY KEY  (`tax_rate_data_id`),
--->UNIQUE KEY `idx_rate_rate_type` (`tax_rate_id`,`rate_type_id`),
  KEY `rate_id` (`tax_rate_id`),
  KEY `rate_type_id` (`rate_type_id`)
)

NEXT PART IN SECOND POST

 
 
Posted: July 2 2008
   |  top
 
Magento Community Magento Community
Magento Community
Magento Community
 
nabuhonodozor
Member
 
Avatar
Total Posts:  38
Joined:  2008-03-27
 

FOR TABLE: tax_rule

CREATE TABLE IF NOT EXISTS `tax_rule` (
  `tax_rule_id` tinyint(4) NOT NULL auto_increment,
  `tax_customer_class_id` smallint(6) NOT NULL default '0',
  `tax_product_class_id` smallint(6) NOT NULL default '0',
  `tax_rate_type_id` tinyint(4) NOT NULL default '0',
  PRIMARY KEY  (`tax_rule_id`),
  KEY `tax_customer_class_id` (`tax_customer_class_id`,`tax_product_class_id`),
  KEY `tax_customer_class_id_2` (`tax_customer_class_id`),
  KEY `tax_product_class_id` (`tax_product_class_id`),
  KEY `tax_rate_id` (`tax_rate_type_id`)
) ;
============
CREATE TABLE IF NOT EXISTS `tax_rule` (
  `tax_rule_id` tinyint(4) NOT NULL auto_increment,
  `tax_customer_class_id` smallint(6) NOT NULL default '0',
  `tax_product_class_id` smallint(6) NOT NULL default '0',
  `tax_rate_type_id` tinyint(4) NOT NULL default '0',
---> `tax_shipping` tinyint(1) NOT NULL default '0',
  PRIMARY KEY  (`tax_rule_id`),
  KEY `tax_customer_class_id` (`tax_customer_class_id`,`tax_product_class_id`),
  KEY `tax_customer_class_id_2` (`tax_customer_class_id`),
  KEY `tax_product_class_id` (`tax_product_class_id`),
  KEY `tax_rate_id` (`tax_rate_type_id`)
) ;

New Table in DB Ver1.0.19870.4 : usa_postcode

There are also small differencies like:

FOR Table: catalog_product_entity_tier_price

KEY `FK_catalog_product_entity_tier_price_group` (`customer_group_id`),
==================
KEY `FK_CATALOG_PRODUCT_ENTITY_TIER_PRICE_GROUP` (`customer_group_id`),

FOR Table: catalog_product_super_attribute_label

ENGINE=MyISAM DEFAULT CHARSET=utf8
==============
ENGINE=MyISAM DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC

Or such small changes like:

KEY `IDX_BASE` (`entity_type_id`,.....
========
KEY `IDX_BASE` USING BTREE (`entity_type_id`,....

Can Somebody from Magento TEAM shear some light to this topic
- do Magento Team is aware of this (sorry to ask but I just want to clear this)
- are changes automatically apply during magento upgrade?
- are some of those changes apply during installation process and are connected to MySQL 4.xx <->MySQL 5.xx hosting enviroment

Best regards,
Piotr

 
 
Posted: July 4 2008
   |  top  |  # 1 
 
Magento Community Magento Community
Magento Community
Magento Community
 
magenkate
Jr. Member
 
Total Posts:  4
Joined:  2008-07-06
 

are changes automatically apply during magento upgrade?
So hard to me.

 Signature 

love tiffany jewelry,gucci jewelry,I want to have Tiffany Ring.So I must work hard.

 
 
Posted: July 7 2008
   |  top  |  # 2 
 
Magento Community Magento Community
Magento Community
Magento Community
 
There4you
Member
 
Total Posts:  67
Joined:  2008-06-24
Tasmania, Australia
 

HI,
I have asked the same thing as I noticed this also.

I would off thought since you asked 3 weeks ago someone would off told us or helped us on this issue. I must say it is dissapointing to see that there is no one to explaint his to us.. :(:( I mean we do not understand everythign that happens or how it works… It makes it that much harder to use the porduct when you do not know how it will go with updates and so on expecailly if you are building a store that you need to rely on.

Slav

 
 
Posted: July 27 2008
   |  top  |  # 3 
 
Magento Community Magento Community
Magento Community
Magento Community
 
There4you
Member
 
Total Posts:  67
Joined:  2008-06-24
Tasmania, Australia
 

After one day of the upgrade I can see that most database stuff have updated themselves, except the flat rate tables, I assume we need t us them before the update happens .... Other issues I noticed that are different are the wording come are cpaital some are small letters not sure if that makes a difference.

 
 
Posted: July 27 2008
   |  top  |  # 4 
 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
    Back to top
 
Dataflow - 500 Internal Server Error
how to overwrite images on import
 
Sales: Call 877.832.5289 (North America) 310.295.4144 (International)
© Copyright 2008 Varien. Magento, eCommerce software, is a trademark of Irubin Consulting Inc. DBA Varien
Privacy Policy|Terms of Service Magento Community Count
50107 users|419 users currently online|102242 forum posts