Re^4: dbicdump and relationships

in reply to Re^3: dbicdump and relationships
in thread dbicdump and relationships

As you can see, it looks like mysql silently ignores references in your SQL statements and doesn't create foreign keys. I would say it is rather nasty behaviour, if it doesn't accept your syntax it should throw an error.

I knew there was something I didn't like about MySQL. I don't think I have that issue with PostgreSQL. :-(

Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg

Comment on Re^4: dbicdump and relationships

Replies are listed 'Best First'.
Re^5: dbicdump and relationships by Anonymous Monk on Jan 14, 2013 at 15:18 UTC
:) sqlt -f MySQL -t MySQL < in > out ... INDEX (`sector`), PRIMARY KEY (`subsector_id`), CONSTRAINT `subsector_fk` FOREIGN KEY (`density`) REFERENCES `densit +y` (`density_id`), CONSTRAINT `subsector_fk_1` FOREIGN KEY (`sector`) REFERENCES `secto +r` (`sector_id`) ) ENGINE=InnoDB; SET foreign_key_checks=1; [download]	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: dbicdump and relationships
by Anonymous Monk on Jan 14, 2013 at 15:18 UTC

...
  INDEX (`sector`),
  PRIMARY KEY (`subsector_id`),
  CONSTRAINT `subsector_fk` FOREIGN KEY (`density`) REFERENCES `densit
+y` (`density_id`),
  CONSTRAINT `subsector_fk_1` FOREIGN KEY (`sector`) REFERENCES `secto
+r` (`sector_id`)
) ENGINE=InnoDB;

SET foreign_key_checks=1;
[download]

[reply]
[d/l]

In Section Seekers of Perl Wisdom