From 0d889a4bb99894e9fdc717398ea0d82564c55583 Mon Sep 17 00:00:00 2001 From: barncastle Date: Tue, 20 Apr 2021 09:05:48 +0100 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 29cf380..d258241 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ A command line tool for exporting World of Warcraft's various DB files to SQL an Exporting the current directory to SQL with foreign keys and table drop: -`MyDBC.exe --c "Server=localhost;Database=test;Uid=root;Pwd=;" --drop true --fk=true` +`MyDBC.exe --c "Server=localhost;Database=test;Uid=root;Pwd=;" --drop true --fk` Exporting the current directory to CSV: @@ -35,4 +35,4 @@ Exporting the current directory to CSV: - `--connection` and `--output` can be used simultaneously. - `--build` is required for all DBs before Legion so that DBCD can load the correct structure. - The tool uses MySQL's `LOAD DATA` command which by default, appends to an existing table. You will need to use the `--drop` argument if this is not desired. -- Unfortunately WoWDBDef "foreign keys" are not supported, only "relations", due to them not lending themselves well to MySQL's optional foreign key constraints. In short; WoW uses `0` whereas MySQL uses `NULL` to dictate a missing reference. \ No newline at end of file +- Unfortunately WoWDBDef "foreign keys" are not supported, only "relations", due to them not lending themselves well to MySQL's optional foreign key constraints. In short; WoW uses `0` whereas MySQL uses `NULL` to dictate a missing reference.