This page lists some samples for how panSL may be used. The first ones demonstrate basic concepts of panSL. These are followed by real world implementations of panSL that are in use today. The last samples show modelling projects typical of an undergraduate University course in Database-modelling. They might also be useful in real-life but they are not tested as such.
You may immediately test any of the samples by clicking on the link 'Try out this schema now!'
| Number | Schema name | Description |
| Schema001 | Simple table | Storing persons with name and address. The most simple form of a panSL-schema. |
| Schema003 | Relations | Showing relations between entities. A person may have zero, one or many friends. A person may own zero, one or many cars while a car may only be owned by one person. Please note that not all possibilities for relations are shown in this relatively simple example. Tree-structures and many-to-many relations are also possible with panSL. See the concept SubName for how you may specify roles like "Owns" and "Is owned by" in relations. |
| Schema004 | Repeated fields, enumerations and logging of changes | Simple demonstration of more basic features in panSL. It is possible to store Many phone-numbers for a person. Gender must be chosen to be one of Male, Female or Unknown (Gender is an Enumeration). All changes to a person entity will be logged. |
| Schema005 | Inheritance, different DataTypes IdentificationUsefulness | Demonstration of inheritance, how a person may be either a Physical person or a Juridical Person. In both cases it is natural to store Contact information and Notes, while date of birth for instance is only natural to register for a Physical person. Date of birth is specified as DataType Date. Note also the use of Essential to specify the most important characteristics of an entity. |
| Schema006 | Tree structures | Demonstration of tree-structures. In this case the tree-structure consists of Growth-potentials for a company. Growth-potentials could have a root-element "Growth" including "Capital" and "R&D". "Capital" could include "Capital assets" and "Financial leverage". "R&D" could include "Number of patents" and "Training budget". Note that it is possible to add IdentificationUsefulness Essential to the "Belongs_to"-PropertyType. This will identify a Growth-potential with the names of all nodes leading to the root. For instance "Number of patents" would be then identified as "Growth R&D Number of patents" making searching easier. |
| Schema100 | Familiy oriented organisation | Can be used as a member-register for any kind of parent-network organisation (any kind of organisation for parents with children who share similar characteristics). A log in is required in order to view any information. The information is shared freely between the members. Parents may edit their own information and the information of related members (spouse and children). This schema is in real world use. |
| Schema101 | Sports club for children | This schema has been made for a sports club where it is desired to register contact information about children and guardians, and to divide the children into various groups. Note how Access in general is specified as Everyone, meaning that a log in is required in order to use the database. But a child's First name, and information about groups of children is public (accessible anonymously). This makes it feasible to create public links on your ordinary website with non-sensitive information without requiring a log in. This should increase the take-up rate of your users. This schema is in real world use. |
| Schema102 | Contacts database simple sales tool | A pragmatic approach to storing contacts with roles and activities. The schema could be used as a simple sales tool. It is possible to show that persons and organisations are related to each other, but not how they are related. The focus has been on quick and easy operation. Note the use of Administrator-privileges restricting access. Log in is possible for all contacts since Mobile_phone is LoginIdentificator, access is therefore restricted to defined Administrators This schema is in real world use. |
| Schema103 | Project hours worked and expenses | A quick and easy to use system for keeping track of work on different projects. The sample shows some use of Functions and use of the Sum-function across relations. See also the ForEach-function if you need more advanced access of related properties. No Access or History-logging have been specified in this sample. |
| Schema200 | Kindergarten with sub units | Could theoretically be used for administering a Kindergarten with multiple sub-units. A lot of details have been thought of in the implementation but the example has not been tried out for real as of March 2012. |
| Schema201 | Hiring process | Could theoretically be used for administering the hiring process for new positions. The schema is belived to work best when relatively few persons apply for a position. |
Last updated 2012-05-02