controller.saveData vs. databaseManager.saveData

According to the documentation, controller.saveData() does the exact same thing as databaseManager.saveData(). IF this is the case, then I suggest Servoy depricate controller.saveData() in future versions. I think it is confusing to leave it there and I’ve seen many cases where programmers do this:

forms.lineItems.controller.saveData()

because they think that in order to save data on the lineItems form they have to use its controller. Simpler is better.

I perfectly agree: forms.xxx.controller.saveData() saves all outstanding changes to the database, not only the changes for the xxx form so it shouldn’t be “form related”.

That’s exactly how it works in 3.5

Do we have a published feature set of Servoy 3.5 yet?

The features were introduced to SAN members last night a general public release will appear a bit later.