No Sequencenumber after newRecord()

Classic Servoy
1

Hi,

I have the following situation:

I have 1 solution and several databases. Using a switch server I connect the solution to the right database. That works and worked ok.

But now I see difference in behavior:

When running my appliction with database A, after a newRecord() I get a sequencenumber from Servoy. Just like expected.
When running my appliction with database B, after a newRecord() I get also a sequencenumber from Servoy. Just like I want it.
But … when running my appliction with database C, after a newRecord() I get NO sequencenumber from Servoy. :-(

I don’t understand how this can happen. I already tried the following:

  • Restart my application server
  • Remove database C from the application server
  • restart AS again
  • Add again database C to the AS
  • Update all sequencenumbers for database C

Nothing helps. It looks like Servoy has disabled the sequencenumbers for database C.
Is there some setting in the repository where I can check that?

Otherwise I don’t see why there is a difference behavior. All databases work with the same solution. The field with sequencenumber is defined as PK and also in the database I see PK defined.

Martin

2

Does this happen in 3.5.8 or 4.1.1?
If it happens in 4.1.1, does it happen in developer or application server? If it’s in developer, what is the value of “startAsTeamProvider” in your servoy.properties file?

3

It happened in 3.5.8 / 3.5.9

I recreated all my databases and for the moment I didn’t see it anymore.
But in case I see it happen again, I’ll will post again.

I’ll see that in the next weeks when I have to test again that solution

4

Martin,

We discovered the issue, it should be fixed in next 3.5 release.

Rob