You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -43,24 +43,24 @@ The tool ignores missing tables and columns when importing the data.
43
43
The key principles are:
44
44
1. More threads are used to speed up data export/import, OOTB all (client)
45
45
machine processors should be used. See `tool_concurrency` parameter in the scripts.
46
-
1. The lowest transaction isolation level is used to make database export/import faster.
47
-
1. Database metadata are used to export/import all user+schema tables to/from a zip file with entries
46
+
2. The lowest transaction isolation level is used to make database export/import faster.
47
+
3. Database metadata are used to export/import all user+schema tables to/from a zip file with entries
48
48
per exported/imported table.
49
-
1. Table and column names are always case-insensitive internally, error is reported when there are more tables
49
+
4. Table and column names are always case-insensitive internally, error is reported when there are more tables
50
50
with the same case-insensitive name.
51
-
1. Concurrent execution requires an extra setup/teardown instructions during data import.
51
+
5. Concurrent execution requires an extra setup/teardown instructions during data import.
52
52
These vary between database types, but they always include disabling/enabling foreign
53
53
key constraints, see database classes defined in the [main package](https://github.com/sranka/jdbcimage/tree/master/src/main/java/io/github/sranka/jdbcimage/main) for more details.
54
54
* All triggers are disabled on Oracle before data import and then enabled after data import.
55
55
* Oracle sequences, when used, are out of scope and usually have to be reset manually after data import.
56
56
* All foreign key constraints are dropped by the tool on Postgress before importing the data, but a table jdbcimage_create_constraints is created with rows that are used to recreate them after data import.
57
57
* Identity column sequences are reset to the lowest value after data import on Postgres.
58
-
1. Streams of data are used for both export and import to have the lowest memory footprint, typically 256M of heap
58
+
6. Streams of data are used for both export and import to have the lowest memory footprint, typically 256M of heap
59
59
memory is good enough. BLOB, CLOBs and lengthy columns still might require more heap memory depending on data
60
60
and JDBC driver in use, so you also might have to increase java heap memory and/or lower batch size used during
61
61
data import. There are parameters in the scripts to do so.
62
-
1. The result files are binary encoded using Kryo and zipped to be small on file system.
63
-
1. The scripts accept several properties as arguments supplied as -property=value pairs
62
+
7. The result files are binary encoded using Kryo and zipped to be small on file system.
63
+
8. The scripts accept several properties as arguments supplied as -property=value pairs
0 commit comments