forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Error: 1060, Duplicate Column Name 'magasin'
- This topic is empty.
-
AuthorPosts
-
-
July 27, 2006 at 1:43 pm #9775violanteMember
:huh: Hi, I have this error message, and there are no duplication of 'MAGASIN' column
Could anyone help me??
Thanks
-
July 27, 2006 at 1:49 pm #22018peterlaursenParticipant
You will need to explain when and how you get this message!
Program version? What are you doing?
Note that column names are ALWAYS case-insensitive in MySQL (also on Linux) so you cannot have a 'magasin' and a MAGASIN' column. That is unlike table names! Just a guess ….
-
July 27, 2006 at 1:56 pm #22019violanteMember
😕 Sorry, i didn't explain a thing 😕
I'm working with SQLyog 5.15, and with migration toolkit, I'm trying to import some tables, and i get that error, but there is only one magasin column, and the name is not duplicated like MAGASIN, for example 🙁
Sorry, if my english is not perfect 😕
-
July 27, 2006 at 2:17 pm #22020peterlaursenParticipant
Migration Toolkit …
That could explain.
Do you import into an existing table?
Check your settings!
Click 'advanced' button .. DDL/DML option
You can attach a screenshot on that TAB …
-
July 27, 2006 at 2:32 pm #22021violanteMember
[attachment=502:attachment]
the table doesn't exist,
Is there a better way than migration toolkit???
-
July 27, 2006 at 2:57 pm #22022peterlaursenParticipant
Whu can't I download this file. What I get cannot be unzipped!
Now take it easy! there is a reason …
What type of database are you importing from?
What happens if you select NOT to 'abort on error' Does everything import OK then?
-
July 28, 2006 at 11:36 am #22023violanteMember
I'm Importing from a COBOL database via ODBC.
When I select not to abort on error, the error is the same, it doesn't import any data at all.
Using MS ACCESS the importation goes just fine, and there are no duplicated column names.
🙁
-
July 28, 2006 at 12:42 pm #22024peterlaursenParticipant
aha .. it looks like this system 'duclicates' the information for some reason.
Any chance that you could help us getting a hold of the ODBC-driver and other software we need to reproduce the problem?
I do not understand why nothing happens when you select not to abort on error.
-
July 28, 2006 at 12:57 pm #22025violanteMember
The ODBC Driver is ACUCORP Version 6.2 but i allready imported other tables from the same database, where the “magasin” column exists (is one of the PK's) and there are no errors 😕
-
July 28, 2006 at 4:23 pm #22026peterlaursenParticipant
We would like to look into this by the beginning of next week!
Please post any addittional observation.
plain ISAM/Cobol files are not uninteresting to us!
-
July 31, 2006 at 7:11 am #22027violanteMember
Hi, I installed SQL Server 2005 Express Edition, and tried to import the table, and the importation was successfull 😮
I also tried the last driver available of AcuODBC (V.7.0) and the problem is still there ERROR 1060 🙁
-
July 31, 2006 at 10:31 am #22028violanteMember
hi!! 🙂
I finaly did some improvements 🙂
Instead of selecting “Copy table(s) from the datasource” I selected “Use a Query to specify the data to transfer” (SQLyog Migration Toolkit);
Now i have another problem, I need the table to be updated daily at 03:00, and I planed a sinchronization, and there's no problem 🙂
My problem is about how to assign the primary keys automatically 🙁
Is it possible to do it in the SQL statement?
Thanks in advance
-
July 31, 2006 at 11:16 am #22029peterlaursenParticipant
Now if you have a query like:
select id as id_targert bigint(20) NOT NULL auto_increment,
e eneum as enum_target ('yes','no') NOT NULL,
It think
select id as id_targert bigint(20) NOT NULL auto_increment,
e eneum as enum_target ('yes','no') NOT NULL,
PRIMARY KEY (id_target)
would work fine.
Doesn't it?
-
July 31, 2006 at 2:16 pm #22030violanteMember
yes, it works just fine 😀
thank you verry much 🙂
I have a table with more than 2.000.000 records from 180.000 diferent articles, for example id_article has 25 records, each one with a different date.
Is it possible when importing with migration toolkit, to place a statement, to import only the most recent record of each article??
The advantage is that the table would have only one record per article 😀
is it possible?
-
July 31, 2006 at 2:56 pm #22031peterlaursenParticipantQuote:Is it possible when importing with migration toolkit, to place a statement, to import only the most recent record of each article??
If you have a timestamp of latest change you can use it with SQL_WHERE
There is also the 'trigger' functionality:
links:
1-> http://webyog.com/faq/17_79_en.html
2-> http://www.databasejournal.com/features/my…p/10897_3550146
-
July 31, 2006 at 4:35 pm #22032peterlaursenParticipant
Back to the problem with ther error.
I think that your table-file must be invalid. Those Cobol/ISAM files are not really protected against that!
Does the Migration Tool mapping dialogue show the column twice? I think that could nbe the issue. Now when you enter a query it will 'take from first instance only'. Also your Cobol application will not care about the second instance – if finds the first and does not care about the rest.
Could you possibly confirm that?
-
July 31, 2006 at 5:08 pm #22033violanteMemberpeterlaursen wrote on Jul 31 2006, 05:35 PM:Does the Migration Tool mapping dialogue show the column twice?
No in the mapping dialog box the column is shown once 🙁
-
-
AuthorPosts
- You must be logged in to reply to this topic.