Skip to main content

mysql separating tables


i made a mistake and i have to split 1 table into 2. i have a product table and i need category table. when i started i only had 1 category per product but not (with new business requirement) i need the ability to put a product in multiple category.



i have a product tables that has a category in it.



here's the table:




product (id, name, category, price etc...)



now, how can i efficiently migrate this without make my site offline?



i have lamp on centos


Source: Tips4allCCNA FINAL EXAM

Comments

  1. Create a table category:

    CREATE TABLE category(id int primary key not null auto_increment, category varchar(40))


    Then select unique categories from product table:

    INSERT INTO category (category) SELECT DISTINCT category FROM product;


    Then create a table for relations:

    CREATE TABLE product_to_category (product_id int, category_id int);


    If you want, you can use foreign keys and constraints.

    Then you can migrate your existing relations:

    INSERT INTO product_to_category SELECT product.id, category.id FROM product JOIN category on category.category=product.category;


    After that, adjust your code to use the new structure and drop the category column from product table:

    ALTER TABLE product DROP COLUMN category;


    Hope this helps.

    ReplyDelete
  2. INSERT INTO new_table_name ("product", "category")
    SELECT id, category
    FROM product;


    Then add a foriegn key constraint on id in new_table_name which references the original product table. After this you can alter table product drop column column_name.

    ReplyDelete
  3. You would start by normalizing your product table - creating 2 new tables:

    CREATE TABLE categories
    (
    cat_id int AUTO_INCREMENT NOT NULL PRIMARY KEY,
    cat_label varchar(40)
    );

    CREATE TABLE product_by_category
    (
    pbc_prod_id int REFERENCES products(id),
    pbc_cat_id int REFERENCES categories(cat_id),
    #indexes for quicker lookup...
    INDEX pbc(pbc_prod_id,pbc_cat_id),
    INDEX cbp(pbc_cat_id, pbc_prod_id)
    );



    INSERT INTO categories(cat_label) SELECT DISTINCT category FROM product;
    INSERT INTO product_by_category(pbc_prod_id, pbc_cat_id)
    SELECT id, (SELECT cat_id FROM categories WHERE categories.cat_label = product.category)
    FROM products;

    ALTER TABLE products DROP COLUMNN category; #do this after you are satisfied with contents of new tables.


    Then you would have to create joins for getting products by category.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex