Page History

...

OSX now have a signed DMG, this has a side effect that the application_server need needs to go inside the app (servoy.app/contents/)

You will get warnings now when using a customer query in a filter with just the "IN" or 'in" operator: "Filter is created using a custom query without using the sql-modifier, this will be removed in a future version of servoy, please use operator 'sql:in'". This is a security enhancement so you are sure the custom query is a valid and fully controlled query that you send to the server. So you as a developer needs to tell the system that this IN can contain custom sql.

Features

Added foundset.getName() (SVY-14449)

Databases who are supporting this (for now only postgresql) will use the ANY (?) instead of IN (?,?,?) when possible for queries. (if there are problems disable this with the property: servoy.server.sql.useArrayForIn=false)

We relaxed the "allow null" in the table editor, you are now able to set that to false after the table is already created
This can have side effects because we can only create this when the table is empty (in developer) or not there yet at all (when deploying) (SVY-14416)

...

The command line exporter now will not just export all components or services anymore if you did not specify any of the -crefs nor -srefs command line arguments. 
It now behaves as the UI does in the developer if you don't manually select anything, and that is that it really only exports what Servoy detects that you are using.
The workaround is if you want the behavior that everything should be exported is to add "-crefs all"