Planned for 1.3.0


  • Network proxy settings

Entity repository manager

  • Driver browser settings
  • Context menu

Entity browser desktop

  • Metadata browser

Entity browser

  • Allow self associations
  • BUG: Subsequent entity browser’s titles are misleadingly named [ROOT]

What’s new in 1.2.0

Entity repository manager

More well known drivers added to driver browser

JDTS driver added to the driver browser.

Entity browser desktop

Inter-repository browsing

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.

Bug fixes

Entity repository manager

  • DATANECT-121: UI freezes when using H2 database.
  • DATANECT-149: NPE in repository navigator on right click when no entity repository exists or is selected

Entity browser

  • DATANECT-124: NullPointerException when no primary key is available but CLOB column
  • DATANECT-125: JDBCType -155 is not a valid value
  • DATANECT-131: Unquoted column names in SQL Statement: BadSqlGrammarException
  • DATANECT-148: BusyIndicator holds focus
  • DATANECT-162: EntityBrowser load timeout


Datanect vision

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.

Primary goal

Datanect should be a data analysis tool that is gives you a fast and clear data insight.


 Secondary goal

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

  • impact on goals
  • affected users

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.