Publishers of technology books, eBooks, and videos for creative people

Home > Articles

Like this article? We recommend

Retrieving Data

Now that we have set up our data source connection, we can begin using that connection to pull information from our database and publish it in our web pages. Let's take a look at how this procedure works:

  1. We create a ColdFusion template that contains instructions (in the form of ColdFusion tags) to retrieve data from the database.

  2. When this template page is requested by a user, the ColdFusion Server software interprets these instructions.

  3. ColdFusion Server then interrogates the database for the appropriate information.

  4. The database responds with a recordset of data.

  5. ColdFusion Server creates an HTML document containing the newly retrieved information and sends it back to the user.

This process is repeated every time that particular template is requested. This means that the user is always provided with up-to-date information from the database. Figure 5 illustrates the steps in this process.

Figure 5Figure 5 Data request process.

Now that we have a connection to the data source set up with ColdFusion Administrator, we need a way to specify what information we want to retrieve from the database. This is done using something called Structured Query Language (SQL). SQL is an easy-to-understand language of simple keywords that can be used to manipulate data in a database. For example, you can use simple SQL instructions to retrieve all employees from a certain department or only those who were hired after a certain date.

In this step, we will concentrate on getting at data that is already in the database. In Step 6, "Updating, Inserting, and Deleting Database Records," we will look at using a web interface to modify existing information in our database.

NOTE

Although SQL is a standard language governed by the American National Standards Institute (ANSI) and the International Standards Organization (ISO), some database systems might use slightly different proprietary dialects. If you are having trouble with SQL statements, check the documentation for your particular database system.

You can find more information on SQL in the "Reference" section of the http://www.LearnColdFusionMX.com web site.

Basic SQL SELECT Statements

Before we can publish database information in our web pages, we have to select the records with which we want to work. This is done with, not surprisingly, a SQL SELECT statement. In its simplest form, we use a SELECT statement to specify the field names we want to use (separated by commas) and which table in the database contains those fields. The following is the syntax for a SELECT statement:

SELECT FieldName1, FieldName2[, etc]
FROM  TableName

For example, to retrieve the names of all of our employees, we would use the following SELECT statement:

SELECT FirstName, LastName
FROM  Employees

This would retrieve the information stored in the FirstName and LastName fields for all the records in the Employees table of our database.

The preceding SELECT statement returns the names in the order in which they are stored in the database. If we wanted to see those names listed alphabetically by last name, we could use the SQL keywords ORDER BY. The ORDER BY clause forces the information to be listed in alphabetical order (or numerical order, in the case of a number field) by the field specified.

For example, the following SQL statement would retrieve the FirstName and LastName fields of all records in the Employees table and would list them in alphabetical order by LastName:

SELECT  FirstName, LastName
FROM   Employees
ORDER BY LastName

By default, this statement will arrange the information in ascending order, A to Z. If you want to have the information listed in descending order, you would use the DESC (short for descending) keyword. To list your employees from Z to A, use the following SQL statement:

SELECT  FirstName, LastName
FROM   Employees
ORDER BY LastName DESC

NOTE

The case (as in upper- or lowercase) of SQL statements usually does not matter. However, many developers put SQL commands in uppercase to make the statements more readable and to make it easier to distinguish SQL keywords from other information contained in the statement.

Using CFQUERY

By passing SQL statements to the database, we are essentially asking questions of the database. These can be questions like, "Who are all the employees in the company?" or "Who works in the sales department?" In database terms, these questions are called queries.

To get ColdFusion to pass a query to a database, we use the <CFQUERY> tag. The <CFQUERY> tag triggers ColdFusion Server to connect to a specified data source, pass a SQL statement, and retrieve the results.

The <CFQUERY> tag requires a closing tag and has two required attributes: DATASOURCE and Name. The Datasource attribute is the DSN of a data source connection that has been established using ColdFusion Administrator. The name attribute specifies a variable that will hold the results of the query when it is returned from the database. We can access the results of the query by calling that variable's name. The SQL statement for the query you want to execute goes between the opening <CFQUERY> tag and the closing </CFQUERY> tag. For example, to get ColdFusion Server to execute a query to our Staff data source, we could use the following block of code:

<CFQUERY NAME="qStaffList" DATASOURCE="Staff">
   SELECT  FirstName, LastName
   FROM   Employees
   ORDER BY LastName
</CFQUERY>

This code would instruct ColdFusion Server to use the data source connection specified with the DSN of Staff. Once connected, ColdFusion Server would pass the SQL statement to list all employees alphabetically by last name. When the database returned the appropriate information, it would be stored in a variable called qStaffList.

Table 1 describes several of the more commonly used attributes of the <CFQUERY> tag. For a complete list of attributes, see the "Reference" section of the http://www.LearnColdFusionMX.com web site.

Table 1 Commonly Used <CFQUERY> Attributes

Attribute

Description

Notes

NAME (required)

The name of the variable that will store the query results

It must follow standard variable naming rules.

DATASOURCE (required*)

The name of the data source to run the query against

This attribute is required unless you are using the ColdFusion Query of Queries feature. See the "Reference" section of the http://www.LearnColdFusionMX.com web site for more information.

MAXROWS (optional)

Specifies the number of records/rows that should be retrieved

Use this attribute if you only want a certain number of records back, such as the top 10 values for a field.

USERNAME (optional)

The username for the database login

Use if the database you are connecting to has security in place and requires a username and password to log in.

PASSWORD (optional)

The password for the database login

Use if the database you are connecting to has security in place and requires a username and password to log in.


Using <CFOUTPUT> to View Query Information

So far, we have only retrieved information with the <CFQUERY> tag. That information is currently stored as a Query scope variable whose name is specified in the <CFQUERY> tag. If we want to actually view this information, we must use the <CFOUTPUT> tag, just as we would with any other variable. When using <CFOUTPUT> with query information, however, there are few additional <CFOUTPUT> attributes to use. Table 2 lists the <CFOUTPUT> attributes associated with outputting query data.

Table 2 <CFOUTPUT> Attributes

Attribute

Description

Notes

QUERY

The name of the variable used to store the query results

This is the name specified in the <CFQUERY> tag's NAME attribute

MAXROWS

The maximum number of rows you want to output

If no MAXROWS attribute is specified, all rows will be displayed.

STARTROW

The first row you want to display

Used commonly in search result sets, such as results 1–10, 11–20, 21–30, and so on.

GROUP

The column or field to group by

Used to output all records from a group together.

GROUPCASESENSITIVE

Yes or No value

Specifies whether the GROUP attribute should be treated as case sensitive.


To display the information we retrieved with the <CFQUERY> previously listed, we would use the following <CFOUTPUT> block:

<CFOUTPUT QUERY="qStaffList">
   #LastName#, #FirstName#<BR>
</CFOUTPUT>

In this code, we use <CFOUTPUT> to display the fields we retrieved using the <CFQUERY> that we named qStaffList. Because we did not specify a MAXROWS attribute, this <CFOUTPUT> block will loop through all the results from our query. We use an HTML <BR> tag in the output to make sure that each employee ends up on a separate line in our web page; otherwise, all the employees will just be listed one after the other on the same line.

Notice that we do not have to output the fields in the same order they were retrieved. In our SQL SELECT statement, we asked for FirstName and then LastName. However, when we output that information, we output the LastName field followed by FirstName. After information has been retrieved using <CFQUERY>, you have great flexibility as to how that information is displayed.

Also notice that we did not specify the Query scope prefix for these variables, such as #qStaffList.LastName#. This is unnecessary because the scope of the variables has been specified by the QUERY attribute of the <CFOUTPUT> tag.

When using the <CFOUTPUT> tag with the QUERY attribute, three additional variables are created. These variables are listed in Table 3.

Table 3 Built-In Query-Related Variables

Variable Name

Description

ColumnList

Produces a list of all the columns/fields returned by a query. Column names are separated by a comma.

CurrentRow

As a <CFOUTPUT> block loops through records in a query result, this variable keeps track of the current record/row number.

RecordCount

This variable contains the total number of records/rows returned by a particular query.


NOTE

If you use one of these special variables inside a <CFOUTPUT> block that uses the QUERY attribute, you do not have to specify a query name prefix for the variable. However, if you are using one of these variables in a <CFOUTPUT> block that does not contain the QUERY attribute, you must specify the name of the query as a variable prefix. For example, the code

<CFOUTPUT>#qStaffList.RecordCount#</CFOUTPUT>

would output the number of records returned by the qStaffList query. In this case, the number is 12.

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email ask@peachpit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.peachpit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020