- Network proxy settings
Entity repository manager
- Driver browser settings
- Context menu
Entity browser desktop
- Metadata browser
- Allow self associations
- BUG: Subsequent entity browser’s titles are misleadingly named [ROOT]
More well known drivers added to driver browser
JDTS driver added to the driver browser.
You can now create instant associations between different data sources. This feature is helpful in distributed environments, e.g. in a microservice architecture. But it is also helpful when you want to connect data between different development stages, e.g. local developer database -> functional test database or integration database. See Help -> Help Contents -> Inter-Repository Browsing for details.
Association tool tips
Associations will show you a tool tips when you put the mouse cursor over them.
Entity repository manager
You might already read the “What’s new in ….” or “Planned for ….” blogs that are about specific versions.
The Datanect vision, or roadmap, blog is about the middle and long term goals that I want to achieve with datanct.
Datanect should be a data analysis tool that is gives you a fast and clear data insight.
Datanect should support you in data export, import and migration.
Based on this goals the priority of tasks, user stories, etc. will be defined. But this doesn’t mean that secondary goal tasks are deferred until all primary goal tasks are done. It means that primary goal tasks will take most of the development power. Secondary goal tasks will take the rest, e.g. a 3/4 distribution.
The main principle of software development at Link Intersystems GmbH is to
build stable and reliable software
Therefore bugs always have a higher priority then new features.
The priority of bugs is determined by
This means that bugs that have a big impact on a primary goal will be highly prioritized even if only a few users are affected. On the other hand bugs that don’t have a big impact but affect a lot of users are also highly prioritized.
That’s why you should not hesitate to send me a bug mail so that I can better prioritize bugs.
You can use the contact form on the home page.
Planned version changed from 1.0.2 to 1.2.0, because of 2 reasons:
Configuration problem markers
The entity repositories will show an error marker if configuration values required to establish an entity session are missing.
A driver browser is added to the entity repository configuration dialog to easily find your driver.
Tabs per entity repository session
For each entity repository session a new tab will be created. Thus you can browse different entity repositories in parallel.
Autofit column widths and browser width
The entity browser’s content tables can now be adjusted to fit it’s content by just one click. Use the autofit button at the upper left corner.
The entity browser window’s width can also be adjusted to fit the content by holding the CTRL key while pressing the autofit button.
Less & greater than filters
Entity attributes can now be filtered using
View area rectanle for the entity selection outline
For a better orientation the entity selection outline does now paint a view area rectangle to make the position of the actual view visible.
Total entity count
The entity browser’s status bar now shows the total number of entities in the repository.
Add / edit / delete entity repositories
The entity repository view’s toolbar contains 3 buttons to manage entity repositories:
Copy entity repositories
Entity repositories can be copied by editing an existing repository and change it’s name.
Drivers from maven repositories
Datanect can download JDBC drivers automatically from any maven repository. Just use the special
mvn:// protocol. E.g. to use a MySQL driver you can set the driver URL to
mvn:///mysql/mysql-connector-java/6.0.6. The format is
mvn://[groupId]/[artifactId]/[version]. It uses your personal maven settings located in
USER_HOME/.m2/settings.xml. Thus you can configure remote repositories, mirrors, proxy servers, etc. as usualy. Take a look at the Maven Settings Reference.
Entity browsers can be tree layouted by their join dependencies using the tree layout button in the toolbar.
Entity browsers can be flow layouted by their join dependencies using a flow layout button in the toolbar. The flow layout brings them in a sequential order.
Refresh of entity browsers
All open entity browsers can be refreshed at once using the refresh button in the toolbar.
Export selected entities
Entities that are selected can be exported via the context menu.
Export selected entity classes
Datanect can export the entity’s metadata as an SQL-DDL script.
Datanect supports export into Excel, XML, XML flat and SQL (insert script). When using SQL export you can also specify the export SQL-dialect. Take a look at DBUnit’s xml and xml flat dataset format description for details on xml export.
An aggregate view can be activated for each entity browser: View -> Aggregate View. The aggregate view shows the aggregation of the actual selection.
Entity selection outline
The entity selection outline helps you to get a quick overview of how many entity are selected in an entity browser. When you put the mouse over the entity selection outline it shows you the id of the entity at that position. You can scroll to any entity by double-clicking onto the entity selection outline.
Improved License View
Automatic update notifications enable/disable
Automatic update notification can now be disabled in the notification window by de-selecting the “Automatic update check” checkbox. Automatic update checks can be enabled again in the same window: Help -> Check for updates