ROCLASI wrote:Just one gotcha...
When you DO use shared connections (i.e. a single DB) then you should keep in mind that when you use Servoy Sequences you are bound to get in a world of hurt. Why?
When you work in Developer you are in fact working from your workspace and not from any repository database (local or shared). All Servoy objects live in your workspace, including the tracking of your Servoy sequences. So when you have 2 or more developers then there are 2 or more places where sequences are kept.
So for instance when you use a shared i18n database with a bunch of developers you should change that database (and your Servoy table settings) to database managed sequences or agree that always 1 specific developer makes the changes (mainly the inserts).
Hope this helps.
That's actually good and bad news Robert. Good in that we can remodel our solution tables to use Db specific sequences, but bad in the fact that I had originally intended that Servoy keep the sequences so we would be truly Db Agnostic.
I think we need to reconsider this. Jasons suggestions above seem like the correct direction, where we share structural updates through SVN and regularly use SQLDump for data updates (mainly 1 developer doing data changes but more than 1 may need to generate test data for development forms etc.).
Obviously this will still entail Db managed sequences.
Cheers Guys - good feedback.