I connected Servoy with the PostgreSQL default database where Servoy installed it’s repository. Is this recommendable or should I create a new one?
Hi Cookie,
cookie:
I connected Servoy with the PostgreSQL default database where Servoy installed it’s repository. Is this recommendable or should I create a new one?
If I read this right you are using PostgreSQL as your repository now and want to use that same connection to setup your solutions tables?
If so this is not recommended. You do indeed need to make a new database and connection for that.
Or did you mean something else ?
Hi
Yes by starting a new solution Servoy installed it’s repository in the default DB of PostgreSQL.
So you are saying it’s best to use two databases and two connections with Servoy? One for the repository and one for the solution?
What is with other solutions? Are they using the same repository?
I’m a bit confused now, because I thought the repository is like a container for solutions, and that they are stored into it.
No confustion necessary.
Repository is used to store the solution data. These data are Servoy proprietary and based on what we do within the designer and during usage of a solution (e.g. store sequences, user data etc.).
Then there is OUR side of the solution. Apart from the design etc. that is stored in the repository we need database tables. These tables can, but should not, be stored in the repository but in a seperate database or databases.
So, in general, the repository is used to store the solution data. We need one or more databases additionally to store the data generated by the user of the solution.
The repository can, and almost always will, hold more than one solution. A database, as defined by us, can also be used to store data form more solutions but that is up to us.
Hope this helps
Thanks for the clarification. I think it’s a good concept.
What if I will work with a hosting provider. Do I have to give him the whole repository DB with my other used DBs once finished?
Yes.
When Servoy is first started at the hosting provider the Servoy_Repository will be setup and this is updated as you add/amend your solutions.
Harjo at Direct ICT provides hosting and is very knowledgable on Servoy generally.
Regards
Graham Greensall
Worxinfo Ltd
Are PostgresSQL views shown as tables in Servoy?
cookie:
I connected Servoy with the PostgreSQL default database where Servoy installed it’s repository. Is this recommendable or should I create a new one?
Hi, one thought: By default database do you by any chance mean template0, or template1?
If you have used any of these, you may end up with your Servoy repository tables copied into every new database you create. Probably not what you intended…
The database calls itself “Postgres”.
There’s a tablespace called pg_default, do you mean that?
And the server name in servoy is “Repository_Server”. Another title doesn’t work.
cookie:
The database calls itself “Postgres”.
That will work fine, but you may end up confused in the long run. It is better to use pgAdmin or some other tool to create a database with some better, more descriptive name, such as “servoy_repository” 
cookie:
There’s a tablespace called pg_default, do you mean that?
That’s fine to use. Unless you plan a really gigantic database where you have to split your data onto several servers.
cookie:
And the server name in servoy is “Repository_Server”. Another title doesn’t work.
That’s the name Servoy uses by default – you can in fact call it anything you like, even “Postgres” 
if you edit the settings in “Database Servers” in Servoy. I have one repository for each project, since I want to keep them separate…
That will work fine, but you may end up confused in the long run. It is better to use pgAdmin or some other tool to create a database with some better, more descriptive name, such as “servoy_repository”
I can rename it. I’m using pgAdminIII, well I’m still trying to figure it out. I probably only have to use 1/10th of it. But I like the neat look of it. The Japanese screenshots look phenomenal. =)
Is it possible to assign a form to a postgreSQL view?