• currently integration tests use default postgres database data
• introduce pre-set database to query on

Points of interest

• src\test\java\cz\blahami2\dbviewer\connections\ConnectionsDetailsApiIT.java

Description

• back-end for saving, updating, listing and deleting connection details for favourite relational database
• exposed via REST
• columns: name, hostname, port, databaseName, username, password (encypher pwd?)

Original text

Implement backend for saving, updating, listing and deleting connection details to you favourite relational database. Those operations should be exposed as REST interface.

E.g. If you choose the MySQL database, you should persist at least the following properties:
· name - custom name of the database instance
· hostname - hostname of the database
· port - port where the database runs
· databaseName - name of the database
· username - username for connecting to the database
· password - password for connecting to the database

Connection details themselves should be stored in database of your choice.

TODO

• add get(id) to API doc
• add validation service

Description

• statistics about each column
  • min, max, avg, median
• statistics about each table
  • #records, #attributes
• documented REST API

Original text

Design and implement REST API endpoints for statistics:
· Single endpoint for statistics about each column: min, max, avg, median value of the column.
· Single endpoint for statistics about each table: number of records, number of attributes.
· Document this REST API

• sonar shows 67% while actual code-coverage is 97%
• for some reason it ignores old tests

• integration tests sometimes fail to finish due to database not being up yet

• DockerRule based tests are in JUnit4
• wrap DockerRule and migrate to JUnit5

• define release process with jgitflow
• apply

https://sonarcloud.io/component_measures?id=cz.blahami2%3Adbviewer&metric=security_rating

• currently only happy scenarios are tested
• add tests for validations, errors, etc.

• src\main\java\cz\blahami2\dbviewer\exceptions\GlobalExceptionHandler.java
• incomplete, handle more exceptions

• enhance with validation service
• currently only basic size/format validation applied

• ConnectionEntity name is wrong
• api endpoints are inconsistent

Description

• browse structure and data using stored connections
• list schemas, list tables, list columns, table data preview
• as much info as possible (data type, primary keys, etc.)

Original text

Design and implement REST API for browsing structure and data using your stored database connections from Task 1. Your API should support the following operations:
· Listing schemas (if your selected database supports them)
· Listing tables
· Listing columns
· Data preview of the table

Resources should contain as much information you can find (data type, if it is primary key, etc.).

• DBeaver
• RESTful
• manage db connections