3 ms·
If this tool is taking data directly from MySQL, why does it need to rely on column names to determine relationships? Couldn't it just see that a column is a fo
by kdazzle 12y ago
If this tool is taking data directly from MySQL, why does it need to rely on column names to determine relationships? Couldn't it just see that a column is a foreign key?
- dreamweapon 12y agoYou or I might think of that as a serious design flaw. But it's just the way developers roll, out in PHP land.
- fubu 12y agohttp://dev.mysql.com/doc/refman/5.1/en/myisam-storage-engine.html#idm47466979839104 http://dev.mysql.com/doc/refman/5.1/en/myisam-storage-engine... See "Foreign key support" in MyISAM Also, in my experience a lot of people do not always use the underlying database constraints even in InnoDB. Not sure if that was the intent of the authors, but just so that others may understand that it could be more than just "PHP land". Might be a little closer to "MySQL land".
- dreamweapon 12y agoThe point is that fundamentally overpowered features of this sort, while potentially quite useful (in some cases), should be optional (and the default setting should point to the non-enabled case). Being as they can certainly make for very rude surprises, when you discover them by chance.
- fubu 12y agoAh, I missed that part of your statement. Snarky comments like "PHP land" while clever and gives us all a big chuckle can be a bit difficult to understand in context. If you actually want someone to understand what you are saying, subtle digs and pretentious put downs, while funny and I'm sure make you feel better about yourself, don't really contribute much beyond dividing people and making others feel bad.