n. pl. sche·ma·ta (sk
-mä
t
, sk
-m
t
) or sche·mas
| A diagrammatic representation; an outline or model.
|
In terms of your Hyperseek system, a "schema" is the term we use to describe your database, tables, and the fields that make up your tables. The database schema is used to tell Hyperseek what fields are contained within a table, and how the program should use them.
Specifically, by properly managing and editing the table schemas, you attain a high level of control over the tables, and how you as the administrator, and your users, interact with them, and work with the data within them.
Schema Definitions give you control over which table fields are visible, what the "viewable name" of the field is, if it's required or not, and even control over the data that is allowed to be entered into the tables.
A default schema is defined for each table in the database (some tables have more than one schema, as they control different views of the table) that should work for you in 99% of the cases. However, you are free to change and tweak schemas as you please.
Nearly Every form that you see and use within Hyperseek is drawn by a "Schema Definition". If you wish to change the appearance of a form (such as the prompts before the inputs, the type of inputs, default values, etc), then edit the "Schema" for that table and the form will render and operate the way that you want.
Some of the more commonly used schemas are listed below:
|
Form Name
|
Sample URL
|
Schema Used
|
|
Add URL Form:
|
accounts.php?action=add_link
|
hyperseek_temp_addurl
|
|
Create New User Account
|
accounts.php?action=create
|
accounts_create
|
|
Edit User Account
|
accounts.php?action=edit_account
|
accounts_user
|
|
|
|
|
|
|
|
|
Schemas are required when writing ds/X Applications, if you want to make use of the iSQL "Record" system. This system provides for a very high-level API that gives you lots of power over table data, and an easy means of drawing input forms, validating data, and saving data to the database. It's certainly not an out and out requirement, but is highly recommended. Please read the ds/X API Documentation if you are writing ds/X applications and would like to incorporate Records and iSQL into your app.