diff --git a/CHANGELOG.md b/CHANGELOG.md index be5bd702..97877d25 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,21 @@ # Changelog +## Version 2.10.4 (26/04/2023) +#### Bug Fixes + +Description are being trimmed of to 30 characters in Microsoft SQL Server #553 +--- + +## Version 2.10.3 (08/11/2022) +#### Enhancements +* Set dbname as command line argument #541 +--- + +## Version 2.10.2 (27/09/2022) +#### Enhancements +* Add missing data to LOB cells #533 +--- + ## Version 2.10.1 (28/06/2022) #### Bug Fixes @@ -309,168 +325,4 @@ To see the help menu use: ``dbptk help migrate``. To check a specific module, `` * ``--import-ssh-host``, ``--import-ssh-user``, ``--import-ssh-password``, ``--import-ssh-port`` or ``--export-ssh-host``, ``--export-ssh-user``, ``--export-ssh-password``, ``--export-ssh-port`` ###### Example: -dbptk migrate --import mysql --import-host localhost --import-user root --import-password 123456 --import-database sakila --import-ssh --import-ssh-host IP Address --import-ssh-user USER --import-ssh-password PASSWORD --import-ssh-port --export siard-2 --export-file /path/to/siard ---- - -## Version 2.4.0 (01/08/2019) -#### New Features - -* Materialised views (as tables) #348 -* Add enhanced support for Sybase ASA DBMS #349 -* Add support for Progress OpenEdge RDBMS #350 -* Denormalize some/all table using foreign keys #351 -* SIARD metadata editing #352 - -Regarding the denormalize some/all table using foreign keys (#351) issue, the option discussed was creating custom views from a SQL query. Check custom views section. -___ - -#### Using the new features: -##### Edit: - -Use `dbptk edit --import-file= [OPTIONS]` - -###### Options: - -`--set`, updates a certain attribute to a new value. -`--list`, lists all the possible changes in a SIARD archive. - -###### Examples: - -* `--set dbname ''`. Updates the dbname attribute to the new value; -* `--set 'schema:' 'table:' 'column:' description ''` . Updates the description of a certain column in a certain table from a given schema; -* `--set 'schema:' description ''`. Updates the description of a given schema. - -##### Custom views: - -When using a JDBC supported import module: -- `-icv ` or `--import-custom-views=` with a path to the query list file; - -###### Example: - -* `dbptk migrate --import mysql --import-hostname= --import-database= --import-username= --import-password= ---import-custom-views= --export siard-2 --export-file=` - -This file should follow the YAML syntax as follows: - -``` -: - : | - query line 1 - query line 2 - (...) - : - : | - query line 1 - query line 2 - (...) - : -``` - -#### Using old features: -##### Migrate: - -Use `dbptk migrate [import module options] [export module options] [ [filter module options]]` ---- - -## Version 2.4.0-RC-4 (17/07/2019) -#### Improvements - -* Add description option to custom view - -Regarding the Denormalize some/all table using foreign keys (#351) issue, the option discussed was creating custom views from a SQL query. Check custom views section. -___ - -##### Custom views: - -When using a JDBC supported import module: -- `-icv ` or `--import-custom-views=` with a path to the query list file; - -###### Example: - -* `dbptk migrate --import mysql --import-hostname= --import-database= --import-username= --import-password= ---import-custom-views= --export siard-2 --export-file=` - -This file should follow the YAML syntax as follows: - -``` -: - : | - query line 1 - query line 2 - (...) - : - : | - query line 1 - query line 2 - (...) - : -``` - -#### Using old features: -##### Migrate: - -Use `dbptk migrate [import module options] [export module options] [ [filter module options]]` ---- - -## Version 2.4.0-RC-3 (18/06/2019) -#### Bug Fixes - -* Fix bug #380 -* Fix bug #381 - -#### Improvements - -* Improve the error handling for custom views feature - -#### New Features - -* Materialised views (as tables) #348 -* Add enhanced support for Sybase ASA DBMS #349 -* Add support for Progress OpenEdge RDBMS #350 -* Denormalize some/all table using foreign keys #351 -* SIARD metadata editing (#352) - -Regarding the Denormalize some/all table using foreign keys (#351) issue, the option discussed was creating custom views from a SQL query. Check custom views section. -___ - -#### Using the new features: -##### Edit: - -Use `dbptk edit --import-file= [OPTIONS]` - -###### Options: - -`--set`, updates a certain attribute to a new value. -`--list`, lists all the possible changes in a SIARD archive. - -###### Examples: - -* `--set dbname ''`. Updates the dbname attribute to the new value; -* `--set 'schema:' 'table:' 'column:' description ''` . Updates the description of a certain column in a certain table from a given schema; -* `--set 'schema:' description ''`. Updates the description of a given schema. - -##### Custom views: - -When using a JDBC supported import module: -- `-icv ` or `--import-custom-views=` with a path to the query list file; - -###### Example: - -* `dbptk migrate --import mysql --import-hostname= --import-database= --import-username= --import-password= ---import-custom-views= --export siard-2 --export-file=` - -This file should follow the YAML syntax as follows: - -``` -schema_name: - view_name: | - query line 1 - query line 2 - ... - another_view_name: | - query line 1 - query line 2 - ... -``` - -#### Using old features: -##### Migrate: - -Use `dbptk migrate [import module options] [export module options] [ [filter module options]]` \ No newline at end of file +dbptk migrate --import mysql --import-host localhost --import-user root --import-password 123456 --import-database sakila --import-ssh --import-ssh-host IP Address --import-ssh-user USER --import-ssh-password PASSWORD --import-ssh-port --export siard-2 --export-file /path/to/siard \ No newline at end of file