This one has been haunting us now for a while. The order of things is this:
import a solution/module for the first time – all tables and fields are created
load the module in Servoy Developer right away – everything is fine
quit developer and dbsrv
restart developer – a random table is sometimes “missing”
open up Sybase Central – the table is there with data in it
when trying to reimport the solution – get an error saying that table “x” – the one missing – is there
if you try to create the table via data providers – you get an error saying the table already exists (but the table is not showing in the list)
The only way we have found to clear this problem up is to delete all the tables the solution uses, reimporting and hoping that all of the tables will be “remembered”. Sometimes it takes us multiple imports with different tables going missing each time before everything settles down. But even then, a week later and a table will go missing.
This was happening summer 2005 and then cleared up for a while. We started noticing again in January 2006. So I wonder if it is an Apple Java issue.
We have had this too. But on Windows. Some table were simply not visible from inside Servoy (usually one table). This only happens with Sybase, I have never seen this on any other database. This made us give up on creating a runtime version…
patrick:
We have had this too. But on Windows. Some table were simply not visible from inside Servoy (usually one table). This only happens with Sybase, I have never seen this on any other database. This made us give up on creating a runtime version…
HUGE tip Patrick. I never would have guessed it was a Sybase/Servoy problem. Moved all data connections over to MySQL 4.0.21 (kept the repository on Sybase) and no glitches whatsoever all day long. It’s amazing how used to working around this problem we’ve become (what a time waste it has been). There should be a warning label: “If you have a big solution comprised of lot’s of modules and database connections, DON’T USE Sybase for your data connections!”
Mass migration of all our clients away from Sybase in progress…
david:
It’s amazing how used to working around this problem we’ve become (what a time waste it has been). There should be a warning label: “If you have a big solution comprised of lot’s of modules and database connections, DON’T USE Sybase for your data connections!”
Mass migration of all our clients away from Sybase in progress…
I assume you mean iAnywhere? What version/build? Are you sure you are using the latest version? We have never seen this happen with the iAnywhere that ships with Servoy 2.2.4 and higher (it did occurr with very early builds of 9.0.1 and JDBC, note this was not a Servoy/Sybase problem but a bug in iAnywhere). I also miss the ‘huge waste of time’ point, perhaps you can explain how your testing procedures are, I would assume that after two runs you can reproduce the problem of disspearing tables so how can it cost so much time? Additionally if you have urgent issues make sure to always file them in our online support system at: http://crm.servoy.com/servoy-webclient/ … oy_support
Make sure to submit a servoy solution that reproduces the issue for a swift response.
Good catch – working with Servoy 2.2.4 but Sybase is definitely an older version. I take it upgrading Servoy versions as they come out does not upgrade Sybase? How would I upgrade Sybase and still keep the data from an older version repository?
This is a tough one. We are 99.99% sure this problem has happened to us with Servoy 2.2.4 in the past on a couple of our production servers. However, we have not been able to reproduce the problem today (for what it is worth).
There is another oddity with Sybase on macs – no matter what I do, the version of Sybase that I show is 9.0.0 (1121). Even with a new install of 2.2.4 into a clean directory. I am checking the version with “./dbsrv9 -v” from the command line. Installing 2.2.4 onto a computer that hasn’t had Servoy or Sybase on it, the version checks out to 9.0.1 (1153). However, the file dates are the same between the two so I am assuming that I am on the latest sybase binaries.
Another thought that occured to me is that maybe creating databases with a different version of Sybase Central than what Servoy is using could be a cause of the problem.
If this happens again in the future, we’ll make sure to nail down the specifics.