Attention to Special Objects

Attention should be given to the following objects:

The Schema Object

• Different database systems have their own interpretation and implementation of this object type
  • MySQL treats a schema object as a synonym for a database object (i.e. CREATE DATABASE = CREATE SCHEMA)    
     
  • PostgreSQL treats a schema as the logical segregation of objects within a database object 
     
• The color of a schema chosen will be reflected in the border color of the respective entities in the ERD pane.
   
• When removing a  schema (using the Delete button), all entities belonging to that schema will be discarded accordingly.
   
• When renaming a schema, if the new name duplicates with an existing schema, you need to use the Merge function (see its button on the menu bar). The merge function lets you choose the new name (among all existing schema) and will move all entities under the old schema to the new one.

The User Type Object

In SchemaBank, we use the User Type object to represent a user defined data type to be used in SQL statements.

If your target database is PostgreSQL, a Domain object will be created from the user type definition during the forward engineering process. 

  In MySQL, there is no such equivalent type. We will write out explicitly the user type definition in each of the SQL statements that carries  the user type.

The Other Object

If you don't find an object type available under the Text Object menu bar, you can consider putting the definition under the Other Object category.

However, please try to refrain from using it unless you really need to, because an Other object would not be easily ported to enjoy new features in future versions of SchemaBank.

Let us know if you think we've missed any database objects in our supported DBMS and we'll deal with it accordingly.