Hi,
Got a ValueList defined as an “All VaLues From” valuelist.
When the underlying data gets updated, the valuelist is not updated. The update of the underlying data is doen in a transaction. The transaction is committed
Before the commit, I put in an extra controller.saveDate() since this helped me before when data was not correctly updated in other places, but that didn’t some things this time.
Paul
Servoy 2.2.4
Mmm, I guess I found the issue: I have (don’t ask why) 2 servers defined, both connecting to the same DB/scheme.
I updated the data through 1 connection and the valuelist that didn’t update was defined over the other connection.
Should that work or not?
For now I just altered the definition of the valuelist and now the update of data is seen.
Paul
Hi Servoyians,
Could you comment if this is a bug, or if this is just not supported?
Paul
Why don’t you merge the two connections, if you only need one?
It is a very simple operation, just use the ‘replace table’ functionality to replace all tables on one connection with tables on another connection in the ‘repository’ window of Servoy developer.
I allready did, got it working now.
But in some cases, using different DB connections is needed, so my question is: have I found a bug, that needs fixing, or have a run into a limitation that we just have to deal with.
Paul
Having two different servers connect to the same database url is absolutely not supported. This will be documented and we will change Servoy so that it will complain if it detects this.
Mmm, didn’t know it was totally not supported. Good to know.
I assume it only goes for multiple connections to the same scheme (where applicable) on the same database?
Meaning: I assume it is supported to have multiple connections to the same DB, as long as you connect to the same scheme?
Paul
It means that you cannot have servers that are basically aliases of eachother. You must connect to different “things”.