SQL Patch question - help please!

[DrByte]

First, if the category you're wanting to move all these products to DOES NOT YET EXIST, you can just move that category to another parent, and rename it if necessary. Bam, done!

But if the destination category already exists and its category-id is important to retain as-is, then you'll need something more complex, like the following:

The category is stored in a couple ways:
1. In the products table there is the master_categories_id ... which basically says which primary/main category the product belongs to
2. And in the products_to_categories table there is an entry for EVERY Product + Category relationship. So if a product appears in multiple categories (ie: is linked to more than one category) then there will be multiple entries in this table, one for each product+category combination.

So, before doing such a mass change, you need to first make sure that the products whose categories you want to make mass changes to are NOT ALREADY "linked" to the destination category you intend to move them to.
One way to do that is to use your Admin and go to that destination category and check whether any of the "linked" products (denoted by the yellow bubble) show there. If they are, then you may want to manually change those by using your Admin to edit that product and change its master and then unlink it (delete it from the other category).

Once your inspection confirms that none of those products are already linked to the destination category, you can do something like the following to MASS MOVE products out of one category and into another;

update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;

You'll get duplicate-key errors if you run that first statement and it finds any of those products already linked to the new category.

Then go and manually delete the empty/obsolete categories using your Admin screen. It's better to do this from your Admin because it does more than just SQL cleanup (ie: also cleans up images, descriptions, languages, related restrictions, and more).

[Feznizzle]

Yippee, thanks Doc!

I just double checked, no linked products. In every case, I will simply be moving products up one level (combining 10 or so subcategories at a time into single higher category). The categories already exist, but I could easily create new categories, then rename them after I have deleted the originals if you think that's the best way to do it. But I'm unclear how to accomplish that... though your summary is very appealing (Bam, done!)!

On the other hand, your mass move instructions seem pretty simple, too. Can I just string a bunch of them together like and past them into the SQL patch like this:

update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;
update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;
update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;

[DrByte]

In every case, I will simply be moving products up one level (combining 10 or so subcategories at a time into single higher category). The categories already exist, but I could easily create new categories, then rename them after I have deleted the originals if you think that's the best way to do it. But I'm unclear how to accomplish that... though your summary is very appealing (Bam, done!)!

"combining" categories can't be done by the simple "move" I was talking about above.

On the other hand, your mass move instructions seem pretty simple, too. Can I just string a bunch of them together like and past them into the SQL patch like this:

update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;
update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;
update products_to_categories set categories_id=NEWNUMBER where categories_id=OLDNUMBER;
update products set master_categories_id=NEWNUMBER where master_categories_id=OLDNUMBER;

Yes.

Here's hoping Ajeh doesn't tell me otherwise!
But she's offline today, so we'll have to play without her.

Of course, always make backups before doing these kinds of things!

[DrByte]

Addendum: After doing this, if you have any pricing features (discounts, sales, specials, etc) specific to the categories you're moving "from" or "to" (or the parents under which they are found), then you'll want to use the Store Manager screen to "Update All Products Price Sorter" so that it recalculates pricing cache data for searches and sorts. Otherwise product price info may be outdated on the storefront.

[Feznizzle]

None of the products are subject to category specific features. However, all have qty based discounting and most have cross sells attached to them. Doesn't *seem* like any of that will be effected.

Of course, always make backups before doing these kinds of things!

Haha. Man, I should earn frequent flyer miles on your Backup mySQL mod, as heavily as I lean on that thing!

[Feznizzle]

Worked like a charm, DrByte! Thank you so much!!!

Now I'm just hoping Ajeh doesn't come back and say this did terrible damage to the db! hahaha

[DrByte]

I asked her to double-check, and she said I did good.

Plus I double-checked the actual PHP code that handles that stuff for one-off cases in the admin ;)