Servoy 2019.03 release candidate 2

Classic Servoy
1

We are pleased to announce the availability of Servoy 2019.03 release candidate 2 (release number 3411)

This version is available through the jar or exe
The update site can’t be used to upgrade from 84 to this release, a bug in the eclipse update mechanisme will result in a broken installation.
So a clean install needs to be done if you come from 84 (but you can reuse the existing workspace just fine)

If you already are on the 2019.03 rc1 install then you can use the update site: http://download.servoy.com/developer/latest/

Release notes of this release 2019.03 whats new

This release fixes a few things for the license manager (to auto upgrade the license when exporting a WAR in developer or command line)

For more info see issues fixed in rc2: 2019.03 RC2 release notes
issues fixed in rc1: 2019.03 RC release notes

The final is planned at the end of March or beginning of April

2019.03 will succeed the 84 release, so there will no more 8.4.x release

From now an Servoy will have a regular scheduler of releasing, so every last month of a quarter after the first week a first RC will be released of that quarter (so next will be 2019.06)
and in the last week of that quarter or the first week of the next quarter the final release will be done.
Check this for more info.

This branch (2019.03) will be promoted to be a LTS release, after we released 2019.06 you can choose to stay on the 2019.03.X LTS branch for the coming year to have only some bug fixes or get the latest updates every quarter.

2

In Servoy 2019.3 rc 2 there is an error showing servers and tables in the developer resources panel. Each server is showing tables belonging to other DBs besides its own. I have a DB called “dbfa_geo” with 6 tables as in this snapshot of Servoy 8.4

The same in Servoy 2019 rc2 shows also tables from other DBs, such as “orders”, “products” and so on as you can see in this screen capture from Servoy 2019.3 rc2

The backend BD is a MySQL 8.0.13, the jdbc driver is also 8.0.13. Is this a bug or what?

3

are you really sure that those tables are not really on that server?
(because of some import where you choose that server as the backend)

I quickly checked a new install of rc2 with the default servers that we have, and those look fine, no duplicate things at all.

4

I checked the MySQL DB and there is no other table besides the six I have created. As you can see in the lower image of my previous post other tables belong to different DBs such as “companies”, “orders” used by Servoy sample solutions. The Servoy 2019.3 was a new install and therefore there should not be any reference to previous DBs. The other DBs seem some kind of ghosts.
Anyway I reloaded tables/table structure from DB and this is what happened

As you can see, now the tables from the dbfa_geo now are visible inside other DBs, such as “example_data”, “log_server” etc.

5

we just can’t reproduce this, it works fine for us at multiply installations on multiply machines
So no idea what did go wrong for you, the urls of the different databases are really all different?

And with a restart it is still invalid?
Do you have dbi files for those servers? what do they tell? What if you remove them for a moment? (move them)