I am working with MYSQL WORKBENCH. After forward engineer I got all my tables in phpadmin.
But the reverse enginner transforms 1:1 to 1:n .
How can I fix this?
Asked
Active
Viewed 1,310 times
1
-
Please explain what "forward engineer" and "reverse enginner" mean. I left those in order not to mess up the question. – shapiro yaacov Oct 29 '15 at 14:46
-
reverse enginnering:https://dev.mysql.com/doc/workbench/en/wb-reverse-engineer-create-script.html – stephane Oct 29 '15 at 14:50
-
Forward Engineering:https://dev.mysql.com/doc/workbench/en/wb-forward-engineering-sql-scripts.html – stephane Oct 29 '15 at 14:54
2 Answers
1
I believe it's a limitation of the forward and reverse engineering processes in MySQL Workbench. The cardinality of the relationship should determine the type of index used for the generated foreign key. Hence a unique index (or a primary key, which is per definition unique) are needed for a cardinality of 1. A non-unique index allows the 1..n cardinality. You cannot model the 0..1 cardinality with foreign keys, however, as foreign keys always require at least one entry (that's their entire purpose, after all).
If you like you can create a bug report (http://bugs.mysql.com) to have this improved.
Mike Lischke
- 48,925
- 16
- 119
- 181
0
Yes,I faced this problem when using django to model 1:1 relationship like this:
class Server(models.Model):
...
asset = models.OneToOneField('Asset', on_delete=models.CASCADE, null=True, blank=True)
after python makemigrations & python migrate, I run mysql workbench(6.3 on ubuntu16.04) reverse engineer,than something show as follow: 1_to_1_bug.png
Evoup Yin
- 1
- 1
- 1
- 2