Entity
Entity is a most important object while configuring your application.
It's main purpose is to store data. Entity is very similar to database table.
Application configuration should start from entires.
All other objects configured upon entities.
(!) An SQL view could be created and used as ordinary entity, server side doesn't distinguish them.
At the bottom of entity field list there are tabs:
- Fields - for entity fields management
- Relations - for entity relations management
- Database script - a preview of SQL script for current entity.
Changes in Database section would not be transfered to database. See Code Cruiser Development Cycle for details.
Entity properties
Section |
Name |
Description |
Basic |
Name |
Name for entity. Should be machine friendly. |
Basic |
Cached |
If true all data from corresponding db table cached on client side (on application start). Used only in native windows client. |
User Interface |
Default Image Color |
Used in native windows client to style the entity buttons. Not used in web client. |
User Interface |
Description |
Useful to make notes about purpose of this entity. |
User Interface |
Display Name |
Display Name is automatically set from corresponding entity field. If display name not changed in query field then any changes in entity field display name would automatically transfer to query field. |
User Interface |
Image |
In native windows client a corresponding image is used to represent an entity. Not used in web client. |
Database |
Data Mapping - Name |
Database name. |
Database |
Data Mapping -Schema |
Database schema. |
Database |
Data Mapping - Type |
Type in database. Table or View. Notice that application server doesn't distinguish these types. |
Database |
Custom Logic On Create |
Just indicates that there is a on create trigger. Currently not used. |
Database |
Custom Logic On Update |
Just indicates that there is a on update trigger. Currently not used. |
Security |
Create |
Select a permission or built in option for security logic. Built in options: <private> means that this option available only on server side. <auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter. Should be set to some value except <private> to use in wizards. Use entities in wizards with caution (can't be used in multitanancy applications), see Row Level Security for details. |
Security |
Read |
Select a permission or built in option for security logic. Built in options: <private> means that this option available only on server side. <auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter. Should be set to some value except <private> to use in wizards. Use entities in wizards with caution (can't be used in multitanancy applications), see Row Level Security for details. |
Security |
Update |
Select a permission or built in option for security logic. Built in options: <private> means that this option available only on server side. <auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter. Should be set to some value except <private> to use in wizards. Use entities in wizards with caution (can't be used in multitanancy applications), see Row Level Security for details. |
Security |
Delete |
Select a permission or built in option for security logic. Built in options: <private> means that this option available only on server side. <auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter. Should be set to some value except <private> to use in wizards. Use entities in wizards with caution (can't be used in multitanancy applications), see Row Level Security for details. |
Created with the Personal Edition of HelpNDoc: Easily create Qt Help files