db sequence not applied while known by Servoy

Classic Servoy
1

The last few weeks I had 2 solutions that use database sequences that started misbehaving. Turned out that a sequence name wasn’t applied correctly. One solution used the sequence name but used the partial name. I saw this in the database server log.
I checked the solution on the server and the sequence name was correctly filled in. After retyping the sequence name it started working properly. :!:

Now today I find a second solution with the same issue. Although this time the sequence wasn’t applied at all although it was filled in in the solution. Retyping it fixed it again.

All this happened after I moved the repository from Sybase to PostgreSQL.
The migration was done by exporting all the solutions and reimporting them into the new database.
On my development machine I have no problems whatsoever with the exact same versions of the solutions.

Before I file a bug report in the bugbase I like to check if anyone else had such experiences?

Servoy Developer
Version R2 2.2.5-build 337
Java version 1.5.0_06-64 (Mac OS X)

2

Hi, definitively worth having someone at Servoy look into this.

Not sure if I have exactly the same problem, but I have sequence issues every time I import into a new repository. Servoy seems to reset my DB Sequences to Servoy Sequences.

3

I’ve seen similar behavior at a client site.

Best,

Rich

4

swingman:
Not sure if I have exactly the same problem, but I have sequence issues every time I import into a new repository. Servoy seems to reset my DB Sequences to Servoy Sequences.

It’s not the same issue.
Your issue can be solved by making sure you check the “Override sequence types to the sequence types contained in the import version” option in the Servoy admin pages. (the option with the big red disclaimer)
When importing using Developer it will ask if you want to override. Just press Yes.

coulombre:
I’ve seen similar behavior at a client site.

Did you see the issue I had or the issue Christian described?

5

I don’t recall… it was early this year.

Rich