Table of Contents Previous Section 

Query Pages

The query page for an entity is shown as a two-column table.

 

The first column in the table lists the entity's properties. The second column contains one or more text fields that let you enter values to query on each property.

A property is either an attribute (a value stored directly in this entity's table) or a relationship (an association between this entity and another entity). For example, in the figure, Title is an attribute and Studio is a relationship. You can use the WebAssistant to hide properties that you don't want users to see.

Note: Direct to Web only displays properties that are class properties. In addition, primary keys and attributes marked as the source of a relationship are hidden by default.

Note that properties are represented in different ways. For example, in the figure, you enter a single string value for Title, while you enter a range of values for Date Released. You can change the representation of most properties using the WebAssistant. In particular, you may want to change how relationships are shown, since by default, you query them by specifying an ID, which is something the user is unlikely to know. See See The Direct to Web Components for more information on the different ways of representing properties in your application's pages.

In the Movie query, to get a list of all dramas released in the 1990's, you would:

1. Enter Drama in the Category field.

2. Enter 1/1/90 and 12/31/99 in the Date Released fields.

3. Click Query DB.

The results are displayed in a list page; see See List Pages .

Table of Contents Next Section