trouble with insert

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
chris0514
Posts: 4
Joined: Wed 09 Sep 2009 09:05

trouble with insert

Post by chris0514 » Fri 21 Jan 2011 04:30

we are trying to copy data from one table to another withing the same mysql database. We can do this with no issue by using mysql command line or the phpmyadmin tool, however when we build the sql to run the insert operation in dbforge studio, dbforge shows the query as a duplicate of the table we want to copy from and the target table (i.e insert into table) never gets any data copied in. We have tried the transaction/commit, the sql and execute but nothing works. the sql statement we are using is:
INSERT IGNORE INTO members (first_name, last_name, home_phone, cell_phone,
first_email, second_email, third_email, fourth_email)
SELECT
members_dads.column1,
members_dads.column2,
members_dads.column3,
members_dads.column4,
members_dads.column5,
members_dads.column6,
members_dads.column7,
members_dads.column7,
members_dads.column8
FROM
members_dads;
with "members being the empty target table and members_dads being the table we want to copy the data from. We are upgrading from studio 3.6 to 4.5 for the import/export funtions and other new tools but will return to the old version if we cant get the insert data tools to work. It probably our misunderstanding of the new version but this is typically a simple process and we cant figure out what is being over looked that would make our insert operations not work. We are hoping for someone out there that can help out. This is a bit of a rush issue so please help, dbforge support welcome also.

Alexz
Devart Team
Posts: 165
Joined: Wed 10 Aug 2005 08:30

Post by Alexz » Fri 21 Jan 2011 08:37

As I understand, you duplicated this post as a ticket to our support system (Ticket ID 25717) and you've already solved this problem. So, I just post it in this topic.

You wrote: "Got it now, used transaction and commit after the insert query and it worked".
It probably our misunderstanding of the new version but this is typically a simple process and we cant figure out what is being over looked that would make our insert operations not work.
I can say only that the INSERT query must be executed in SQL Editor as any other one. This is the main functionality that must work every time and in every version of the product. And, of course, this is just a simple execution of the script to the server.

If you have any other questions, feel free to contact us.

Post Reply