Overview

PhixFlow ERDs define the logical structure of the data in your application. 

The following example shows an ERD for a school. A school has entities, for example: departments, teachers, students, classrooms and so on. All these entities are represented as streamtables. The lines connecting the Tables show the Relationships between them.

The table has a list of attributes, which represent the different pieces of data you want to record. For example, the Student stream in the ERD above has the attributes: UID, Address, IntakeYear and Name.

Attributes are configured with a data type and associated properties, for example the Name and Address attributes are "String" types. To change the attribute to reflect the nature of your data, click on the attribute name to open it's properties, here you can set its details including the data type. For example, IntakeYear is set to Date. It is important to set the correct data type and properties before loading records into a table, as you cannot change the data type once the table stream contains records. If you do have data and want to change the type you will need to add a new attribute or clear your data see Rollback Recordsets.

Primary Keys and UIDs

PhixFlow expects every table to have a special attribute called a primary key, which uniquely identifies each record. For example, teachers have a UID as the primary key. This is because they can have the same first or family name, or even both, so these attributes cannot be a primary key. When you create a streamtable, PhixFlow adds an attribute called UID (short for Unique IDentifier) and configures it as follows:

• as the table's  primary key.
  If you look at the School ERD example above, you can see that every stream has an attribute called UID, and that it has the primary key icon next to it.
• as an integer; see the SchoolDept primary key properties on the right.
• to automatically create a unique number for every record in a table.

This means PhixFlow can ensure all the UIDs have unique values. 

Display Name 

Anchor
display-name display-name

Typically a Primary key is not user friendly and you do not want to display it. Instead you want to display something more suitable for a human, for . For this reason, when you create a table PhixFlow automatically adds an attribute called Name and ticks the Display Name property. The Display Name does will be shown in place of the Primary Key when displayed on a View. Display Names do not need to be unique and should be something more user friendly.

Lets look at the following example:

The SchoolDept table is created and PhixFlow has created both a UID setup by PhixFlow, for example 1490 or 1550, and a Name, for example Mathematics.

To help users make sense of this PhixFlow will display the department name, such as Arts or Science's Name, when when any relational view makes reference to the SchoolDept using it's Primary Key. See Relational Views for more information. The configuration is shown below:

    SchoolDept                         SchoolDept 
    primary key                           Name Display Name 

Relationships and Foreign Keys

Tables in PhixFlow are relational., which means you means information in one table can be related to or link to information in another table. The kkey benefit is you can access data in many different ways tables without needing to duplicate data.

In the ERD you can connect tables by drawing a line, called a relationship between them.

For example, the Teacher table needs to have the name of a department. The ERD below represents this relationships using a line that joins tables: the SchoolDept table SchoolDept DeptID to the Teacher tableTeacher Department:

When you create screens that show data, PhixFlow uses the relationships from the ERD to provide options for displaying data from related attributes in the same grid, form, card, graph or chart; see Understanding Data Views. This means we only need to store the School DeptID against a teacher, but we have access to all of the SchoolDept details such as Name.

When you create a relationship from a primary key to an attribute, PhixFlow automatically sets the attribute to be a foreign key.   Foreign keys can have different names to the primary key, but they must have the same data type and properties as the corresponding Primary Key. For example in the illustration above, the Teacher.Department attribute contains the same values Data Type as SchoolDept.UID; as shown in the attribute properties on the right. However, in the Teacher stream there may be more than one .DeptID.

The foreign key represents the many side and the primary key the one side. This means that SchoolDept.DeptID is unique, there is only one record containing this unique information. The Teacher.Department, can have one or more instance of a value of DeptID. For example, the Maths Department UID could occur 10 times, once for each of the 10 maths teachers.

Although the relationship is between the primary key and a foreign key, when the foreign key is included in a screen, PhixFlow shows the attribute that has Display Name selected, which is the Name attribute by default. This gives the user a the meaningful string, rather than the primary key's identifier. For example, a stream showing Teacher.Department will have data such as Arts or Science, rather than an ID like1490.

Attribute properties for:

   ClassRoom
   Department

Image Removed

One-to-many and Many-to-one

PhixFlow always draws a relationship line between a primary key and a foreign key. This represents a 1:many relationship. The "many" end of the line has several lines. For example, one teacher runs many courses.  A many:1 relationship is implied when you read a relationship in the opposite direction. For example, a department has many teachers, and several teachers work for one department.

Many-to-many 

To create a many-to-many relationship, you need an intermediate stream table that has foreign key attributes from each of the streams tables you want to have a relationship. For example, many students take many courses. A many-to-many relationship is shown below, using the intermediate stream table called CourseAttendee. Notice that CourseAttendee does not need a unique identifier.

• A course is attended by many students
• A student takes many courses.

Using ERDs in Views

ERD's are important because the streamstables, attributes and relationships define the logical structure of the data that your application uses. PhixFlow displays this data to application users via views Views. Most commonly this will be a grid view, which displays data in table rows and columns.

The concept for a view is described below and illustrated on the right:

1. Start with a specific streamtable, which is the base stream for the view.
2. Select the attributes from the base stream table that you want to be the columns in the grid.

3. From related streamstable, select other attributes to add more columns to the grid.

4. NotePhixFlow can only display data from a related primary key.PhixFlow joins the related streams tables via their relationships.
   Under-the-hood this is done using a direct SQL join.

1. .

Why You Cannot Show Data from 1:many Attributes

If you add an attribute from a stream that is related to the base stream table via a 1:many relationship, PhixFlow does not show any data in the grid rows. This is because there may be many values, which cannot be displayed in a single cell of the grid.

I am here - the following section should probably go .

Displaying Names Not Identifiers

Streams are related via primary keys. If a stream has a foreign key attribute and you use it in a grid view, the column displays the identifier. You can see this in the Teacher column below.

Image Removed

This can be put into the compiling views bit maybe

When creating the view, you need to choose a stream to be the base stream. Your choice depends on the records that you want to show, as it is the base stream's records that are displayed. In this case I want the records from the course stream, in which there is one record for each course, so when I create the view I start with this stream.

Image Removed

The left of the Attribute Selector / View Editor window lists related streams. By selecting the Teacher stream, I can add the Department attribute to the grid view.

Image Removed

For details of creating views and using the attribute selector see Understanding Data Views and Showing Data on a Screen.

Editing Data in a View

When you create a view that includes attributes from related streams, only data from the base stream is editable. For example, using the view in the example above, you could create a form to add a new course, with fields for:

• Department
• Course
• Classroom
• Teacher.

Creating PhixFlow Streams From Existing Data

You can create streams table in an ERD, but this is time consuming. If if you already have data, PhixFlow can create streams tables from it.