Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
filereference:dbssystem [2022/08/17 10:23] – [System Database and User/Project Database: Basic Concept] enviadmin | filereference:dbssystem [2022/12/06 21:53] (current) – [System Database and User/Project Database: Basic Concept] enviadmin | ||
---|---|---|---|
Line 32: | Line 32: | ||
The **//System Database// | The **//System Database// | ||
- | === {{: | + | === User Database === |
The **//User Database// | The **//User Database// | ||
Line 44: | Line 44: | ||
=== Project Database === | === Project Database === | ||
- | {{: | + | As said above, there is always one global user-editable database in the ENVI-met system that can be used in all simulations in all projects. |
However, if you have a lot of different projects or very specific projects, it might not be the best idea to store all the user-defined items in one big database. Especially if you want to adjust certian properties of items, e.g. soil materials, for certain simulations or projects, it might be undesirable that these material changes will effect all other simulations as well - which will be the case if edited in the global User Database. | However, if you have a lot of different projects or very specific projects, it might not be the best idea to store all the user-defined items in one big database. Especially if you want to adjust certian properties of items, e.g. soil materials, for certain simulations or projects, it might be undesirable that these material changes will effect all other simulations as well - which will be the case if edited in the global User Database. | ||