4 ms·
No foreign key support is kind of a deal-breaker. Hard to believe anyone who is actually in the position of needing this would have a schema so simple that it c
by bjacobel 12y ago
No foreign key support is kind of a deal-breaker. Hard to believe anyone who is actually in the position of needing this would have a schema so simple that it contains no foreign keys.
- warbiscuit 12y agoHard to believe mysql doesn't include that data in one of it's dump formats.
- morgo 12y agoIt is supported, just not in XML dump format.
- warbiscuit 12y agoAh. That's a relief, I was a little worried. But that makes it strange that someone, knowing of this limitation, would choose to start with the xml dump format.
- barking 12y agoI think the fact that this form of dump doesn't contain foreign keys is even more extraordinary. What's the point of having a dump format that you can't use to restore your database properly? Does it have a health warning advising that it's not a proper dump?
- danneu 12y agoIt contains the foreign key data, but not the constraint. You get this: <field Field="course_id" Type="int(10)" Null="NO" Key="MUL"/> But not this: CONSTRAINT `fk_courses_offered_class_details` FOREIGN KEY (`course_id`) REFERENCES `courses_offered` (`id`)
- maaaats 12y agoWell, I've had issues with pg_dump's standard format. It can't be directly used to restore a db, one must manually set it to dump a .bak or something else.
- jeltz 12y agoNot sure what you refer to here. All pg_dump formats should work for restoring a database. The only flaw in pg_dump that I know of is the mess if you want to dump an entire cluster of databases but still have one file per database.
- chris_wot 12y agoHow?
- maligree 12y ago> so simple or complex