Hi All,
I have some doubt regarding the Servoy Repository.
In Servoy, all the Application data are get stored in the repository that is our iAnywhere sybase database.
Can we use a different database connection(SQL supported) for this purpose?
And,
Let 4 to 5 developers are working on a single project. So, how Servoy meets all the SCM(Source Code Management) Requirements ?
Another question,
Can a number of Servoy developers work on a same repository?
Thanks,
Acer
Acer:
Hi All,I have some doubt regarding the Servoy Repository.
In Servoy, all the Application data are get stored in the repository that is our iAnywhere sybase database.
Can we use a different database connection(SQL supported) for this purpose?
If I understand you right you store your data in the same database as the repository ?
It’s very much recommended to keep the repository db for the repository only.
So yes, you can use another database (and corresponding connection) for your data.
Acer:
And,
Let 4 to 5 developers are working on a single project. So, how Servoy meets all the SCM(Source Code Management) Requirements ?
I’ll let one of the Servoyans answer that one.
Acer:
Another question,Can a number of Servoy developers work on a same repository?
That’s what Multi-developer is designed for.
Hope this helps.
Thanks Robert,
For your response.
ROCLASI:
If I understand you right you store your data in the same database as the repository ?
Yes.
ROCLASI:
It’s very much recommended to keep the repository db for the repository only.
Can you please explain it.
ROCLASI:
That’s what Multi-developer is designed for.
Multi-developer is same as our Servoy Developer or different?
Thanks,
Acer
Multi developer is another product than developer but the basis is the same.
You can use client data and repository data in the same database but it is not recommended. They are not related.
When you keep them separate you are much more flexible regarding switching databases, no potential integrity issues etc.
Thanks Marcel,
For your response.
I want to switch my repository Server to Oracle, without any loss of previous data.
Then, How can i do that?
Thanks,
Acer
You can export your solution with sample data and re-import it into your new repository.
That should be enough.
Easiest way is to export your solutions via Developer (menubar > File > Repository).
Point Servoy Developer to your newly created Oracle db and re-launch Developer.
It will create the tables it requires and after this you can import your exported solutions (menubar > File > Repository).
Hope this helps.
Sorry, i am new to Servoy that is why i am not quite familiar with it.
I am able to create a connection to Oracle db, but how can i tell to Servoy that use this database connection to store Application data.
That mean,
We can create a number of database connection under edit → preference → db server, And how we declare one of them as a repository server?
I think, I have to rename it to “repository_server”, isn’t it?
Thanks,
Acer
You connect the server with a db dedicated to the repository.
You name the connection (not necessarily the db) servoy_repository and restart Servoy.
When all goes well Servoy will create the necessary tables at startup.
After the new repository is created you choose repository from the filemenu and start importing your solution.
Don’t forget the export the solution from the old repository first
IT2Be:
You connect the server with a db dedicated to the repository.You name the connection (not necessarily the db) servoy_repository and restart Servoy.
When all goes well Servoy will create the necessary tables at startup.
After the new repository is created you choose repository from the filemenu and start importing your solution.
Don’t forget the export the solution from the old repository first
Thanks Marcel,
Please see the bold text.
But in default, the repository server is named as “repository_server”, isn’t it create any problem?
Thanks,
Acer
Hi Acer
The actual database for the Repository can be called anything you like: ‘repository_server_sybase’, ‘repository_server_oracle’ etc.
But the database connection name that you setup in Edit/Prefs must be called ‘servoy_repository’.
You can retain the old repository connections by renaming them to ‘servoy_repository_old’ or similar then create a new connection called ‘servoy_repository’ and point this at the new database that you will use as the repository - ie ‘repository_server_oracle’.
Close down Servoy - and remember to stop Sybase if its running - then restart Servoy and it will create a new repository in ‘repository_server_oracle’
HTH
Graham Greensall
Worxinfo Ltd
No Acer is right in that the connection name has to be ‘repository_server’, not ‘servoy_repository’.
The database name itself can indeed be whatever you like.
Hi Robert,
Now, it is clear to me.
And also i have set it up.
Thanks to all being join with me on this discussion.
Still i have the one previous doubt.
Acer:
Let 4 to 5 developers are working on a single project. So, how Servoy meets all the SCM(Source Code Management) Requirements ?
SCM Requirements such as
Versioning is supported by Servoy, but about another three?
Thanks,
Acer
Well I know for sure forking is not supported.
As for the other 2 I dunno, maybe Multi-Developer does something like this.
But if you want all this I think you have to wait for Servoy v4.0. That will be supporting CVS/SVN in some manner.
Ahhh - the dangers of doing things from memory
Thanks for the correction.
Graham
Indeed, anwered ‘by heart’
Acer:
SCM Requirements such as
- Locking and Concurrency Management
- Versioning and Revision History
- Synchronization
- Project Forking, etc.
Versioning is supported by Servoy, but about another three?
jaleman:
- is what Servoy Multi Developer does
3 and 4 to some degree, but will be fully supported in Servoy.Next (most probably 4, come to ServoyWorld to learn more!)
Thanks Jan,
for the Info.
From where i will get Servoy Multi Developer?
Thanks,
Acer
You can order Multi-developer from the Servoy store
Thanks Robert,
Thanks,
Acer