Skip to content

Commit 02c120c

Browse files
committed
Elaborated on database name prefixing and data-only aspect in README.md
1 parent bf79244 commit 02c120c

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

README.md

+7
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ dbdpp source.cnf target.cnf ref_table target_table > out.sql
4040
```
4141
will print into **out.sql** list of SQL statements which should be applied to
4242
_db_to_change.target_table_ to make it consistent with _db_reference.ref_table_.
43+
Only INSERT/UPDATE/DELETE statements are generated; there will be no ALTERs,
44+
as _dbdpp_ only work for tables with matching structure (the same set of fields and primary keys).
4345

4446
There are two modes of operation:
4547
* if both **source.cnf** and **target.cnf** are given (even if they are the same),
@@ -49,6 +51,11 @@ There are two modes of operation:
4951

5052
Choose the option that is better for your particular case performance-wise.
5153

54+
The database names can be entered in the ***.cnf** files, _and/or_ you may include them in command line arguments
55+
as `my_db_name.my_table_name`. These names will neither be escaped nor quoted, so whatever you pass as a table name
56+
will be used as-is both in _performed_ and in _generated_ SQL queries. Therefore, if you do not specify the database
57+
name as a prefix for the table name, none will be added to generated INSERT/UPDATE/DELETE queries.
58+
5259
## How to compile?
5360

5461
### Requirements

0 commit comments

Comments
 (0)