Member Avatar for craign924

hello forum,

i work with oscommerce and i have to upgrade from 2.2 to 2.3.

since all my tables --products, categories etc. are in 2.2 i thought i would just
install 2.3 and then import the 2.2 db and viola!! but it did not, and does not work
like that.

i was given the advice to install 2.3 and then change the structure of the 2.2 db
to match the 2.3 db and then import only the certain tables needed.

i sure i can do this in phpmyadmin, but i would have to do this manually.

i thought i would come and ask if there is a utility or some simpler more effecient
way of doing this.

if someone could advise or refer me to an example or tutorial or article referring
to this scenario, i would be grateful.

thanks,
craig

  • 4 Contributors
  • 3 Replies
  • 103 Views
  • 14 Hours Discussion Span
  • Latest Post Latest Post by Stefano Mtangoo

Dani AI

Generated

As suggested, the osCommerce community is a good reference, and and pointed in the right directions. The failure seen when importing a 2.2 dump into a fresh 2.3 install is normally caused by schema differences (new tables, new columns, changed defaults/keys). The safest approach is: install 2.3 on a dev server, compare the two schemas, generate the ALTER/CREATE statements needed, then import data-only for the stable tables.

A reproducible workflow that avoids manual per-column edits:

Create schema-only dumps and diff them to see structural changes:

mysqldump --no-data -u root -p oscommerce22 > oscommerce22_schema.sql
mysqldump --no-data -u root -p oscommerce23 > oscommerce23_schema.sql
diff -u oscommerce22_schema.sql oscommerce23_schema.sql > schema.diff

Use the diff to craft ALTER statements or feed a schema-sync tool.

Move core data (not full DB) with data-only dumps for selected tables:

mysqldump --no-create-info -u root -p oscommerce22 \
  products products_description products_to_categories customers orders \
  > core_data.sql

mysql -u root -p oscommerce23 < core_data.sql

Exclude runtime/admin tables (sessions, cache, admin users) and review configuration entries manually because keys or expected values may differ between versions. If InnoDB is used, wrap imports with SET FOREIGN_KEY_CHECKS=0; then re-enable.

If a GUI or automated option is preferred, use a schema-compare/synchronize tool (MySQL Workbench schema diff, dbForge Schema Compare, or mysqldump+diff as above) to generate ALTER scripts. Always work on a copy, keep full backups, test the frontend and admin functions after migrating, and verify auto-increment values and any custom add-ons/extensions for compatibility with 2.3 before going live.

Recommended Answers

All 3 Replies

Member Avatar for Member #120589

have you tried the oscommerce forum. Although you may strike it lucky with a member that has used osc, the site itself should be the best place to ask specific questions with regard to the product.

Member Avatar for Stefano Mtangoo

as for tool MySQL workbench is better than PHPMyAdmin

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.