only one model in a database ???

[CapJo]

I'm using a postgres repository and I have created a database with the name "EA".

After using Tools -> Data Mangement -> Data Transfer, in a database where a model already exists the old model will be deleted.

Do I have to create for each model a own database, for example "NEW_MODEL" or it's possible to have more models in one database?

A other solution is to have for each project a own package in one model, but if you want to hide information it's not the best way.

[Jan ´Bary´ Glas]

The way of two root packages works. But if you want to use two independent models, I'd advise using two separate databases (on the same server) anyway.
I can't see the point of having 2 models in one repository, can you give an example?

[CapJo]

We have to rent a database server and we have no adminstrative rights on it so it would be a problem to create new databases.

"Root Project Packages" are already used to structure big projects.

The Problem is that you can only define "view packages" in "Root Project packages". In "view packages" you can only define ordinary packages.

[Jan ´Bary´ Glas]

In "view packages" you can only define ordinary packages.

I see. Maybe someone from Sparx will help?

[sargasso]

CapJo said

We have to rent a database server and we have no adminstrative rights on it

Now that has got to be the most insane thing I have heard in over 28 years in this industry.  Developers with no admin rights over their own data in their own domain.  I suppose they wont let you have a text editor either in case you actually write some [shudder] code [/shudder].

One of the biggest points of postgres is that you can set up user domains that are entirely compartmentalised against other users & databases.

CJ, you are being conned, duped and had!

b