Home > Articles > Programming > PHP

Multiple Database Interaction in PHP 4.1

May 30, 2003

📄 Contents

␡

Advanced Database Interaction in PHP4
Database-Specific Functions in PHP
DBX—PHP Support for Multiple Databases
Creating Your Own Support for Multiple Databases
Using Pear::DB

⎙ Print

< Back Page 4 of 5 Next >

This chapter is from the book 

Advanced PHP for Web Professionals

Learn More Buy

Creating Your Own Support for Multiple Databases

If you have a simple application that doesn't require complex database interaction, but you still want it to work with multiple databases, then you can create your own set of database wrapper functions.

You have to take into account the different database-specific limitations that may arise and code to the lowest common denominator. That is, you can't use the useful "AUTO_INCREMENT" column feature that is supported in MySQL if you also want to support MS SQL or PostgreSQL databases, since they do not implement that feature. Similarly, MySQL doesn't support secondary keys, so you cannot use that convention.

This next example provides a sample database wrapper that supports MySQL, MS SQL, and PostgreSQL databases. It is called DBlib and contains the following functions listed in Table 3–1:

TABLE 3–1 DBlib.php Functions

FUNCTION	DESCRIPTION
connectDB(DB_ID)	Connects to the database server and returns a DB_CONNECTION.
selectDB(DB_ID)	Selects which database should be used on the server.
queryDB(DB_ID, QUERY)	Sends an SQL query to the database. Returns a RESULT set.
returnDBarray(DB_ID, RESULT)	Returns an array of a row in the RESULT set.
numrowsDB(DB_ID, RESULT)	Returns the number of affected rows from the last query.
closeDB(DB_ID, DB_CONNECTION)	Closes the connection to the database.

The first part of the example is the DBlib.php file, which you include in your own application.

Script 3–2 DBlib.php Script 3–3

    1.  <?
    2.  function connectDB($db) {
    3.      global $host, $database, $username, $password;
    4.      switch($db) {
    5.          case ("psql"):
    6.              $conn_string = "host=" . $host . " 
dbname=" . $database . " user=" . 
$username . " password=" . $password;
    7.              $dbconn = pg_connect($conn_string) or 
die ("Error Connecting to PostgreSQL DB");
    8.              return $dbconn;
    9.              break;
  10.          case ("mysql"):
  11.              $dbconn = mysql_connect($host, $username, $password) or 
die ("Error Connecting to MySQL DB");
  12.              return $dbconn;
  13.              break;
  14.          case("mssql"):
  15.              $dbconn = mssql_connect($host, $username, $password) or 
die ("Error Connecting to MS SQL DB");
  16.              return $dbconn;
  17.              break;
  18.          default;
  19.              echo "<P>Invalid Database: $db";
  20.              return 0;
  21.          }
  22.  }
  23.
  24.  function selectDB($db) {
  25.      global $database;
  26.      switch($db) {
  27.          case ("psql"):
  28.              return 1;
  29.              break;
  30.          case ("mysql"):
  31.              mysql_select_db($database) or die ("Error Connecting to MySQL DB");
  32.              return 1;
  33.              break;
  34.          case("mssql"):
  35.              mssql_select_db($database) or die ("Error Connecting to MS SQL DB");
  36.              return 1;
  37.              break;
  38.          default;
  39.              echo "<P>Invalid Database: $db";
  40.              return 0;
  41.          }
  42.  }
  43.
  44.  function queryDB($db, $query) {
  45.      switch($db) {
  46.          case ("psql"):
  47.              if(!$result = @pg_exec($query)){
  48.                  $result = 0;
  49.              }
  50.              break;
  51.          case ("mysql"):
  52.              if(!$result = @mysql_query($query)){
  53.                  $result = 0;
  54.              }
  55.              break;
  56.          case("mssql"):
  57.              if(!$result = @mssql_query($query)){
  58.                  $result = 0;
  59.              }
  60.              break;
  61.          default;
  62.              echo "<P>Invalid Database: $db";
  63.              $result = 0;
  64.          }
  65.      return $result;
  66.  }
  67.
  68.  function returnDBarray($db, $result) {
  69.      if($result != "error") {
  70.          switch($db) {
  71.              case ("psql"):
  72.                  if(!$array = @pg_fetch_array($result)){
  73.                      $array = 0;
  74.                  }
  75.                  break;
  76.              case ("mysql"):
  77.                  if(!$array = @mysql_fetch_array($result)){
  78.                      $array = 0;
  79.                  }
  80.                  break;
  81.              case("mssql"):
  82.                  if(!$array = @mssql_fetch_array($result)){
  83.                      $array = 0;
  84.                  }
  85.                  break;
  86.              default;
  87.                  echo "<P>Invalid Database: $db";
  88.                  $array = 0;
  89.          }
  90.          return $array;
  91.      }
  92.  }
  93.
  94.  function closeDB($db,$dbconn) {
  95.      switch($db) {
  96.          case ("psql"):
  97.              if(!@pg_close($dbconn)){
  98.                  return 0;
  99.              } else {
100.                  return 1;
101.              }
102.              break;
103.          case ("mysql"):
104.              if(!@mysql_close($dbconn)){
105.                  return 0;
106.              } else {
107.                  return 1;
108.              }
109.              break;
110.          case("mssql"):
111.              if(!@mssql_close($dbconn)){
112.                  return 0;
113.              } else {
114.                  return 1;
115.              }
116.              break;
117.          default;
118.              echo "<P>Invalid Database: $db";
119.              return 0;
120.          }
121.  }
122.
123.  function numrowsDB($db, $result) {
124.      switch($db) {
125.          case ("psql"):
126.              if(!$rows = @pg_numrows($result)){
127.                  return 0;
128.              } else {
129.                  return $rows;
130.              }
131.              break;
132.          case ("mysql"):
133.              if(!$rows = @mysql_numrows($result)){
134.                  return 0;
135.              } else {
136.                  return $rows;
137.              }
138.              break;
139.          case("mssql"):
140.              if(!$rows = @mssql_num_rows($result)){
141.                  return 0;
142.              } else {
143.                  return $rows;
144.              }
145.              break;
146.          default;
147.              echo "<P>Invalid Database: $db";
148.              return 0;
149.          }
150.  }
151.
152.  ?>

Script 3–2 DBlib.php Line-by-Line Explanation

LINE	DESCRIPTION
2	Declare the connectDB function. The function requires the type of database ($db) as an argument.
3	Declare global variables that can be accessed by this function. The variables are required to connect to the database.
4	Start a switch statement that checks to see which of the cases should be run, depending on the value of $db.
5	If $db = "psql", then the user wants to use a PostgreSQL database.
6	Generate a connection string for a PostgreSQL database.
7	Execute the pg_connect() function to connect to the PostgreSQL server. If there is an error, then kill the script and provide an error message.
8	If there is not an error, then return the $dbconn variable, which is the database connection handler and is required for many of the other functions.
9	Break out of the switch statement, since the case has been satisfied.
10	If $db = "mysql", then the user wants to use a MySQL database.
11	Execute the mysql_connect() function to connect to the MySQL server. If there is an error, then kill the script and provide an error message.
12	If there is not an error, then return the $dbconn variable, which is the database connection handler and is required for many of the other functions.
13	Break out of the switch statement, since the case has been satisfied.
14	If $db = "mssql", then the user wants to use a MS SQL database.
15	Execute the mssql_connect() function to connect to the MS SQL server. If there is an error, then kill the script and provide an error message.
16	If there is not an error, then return the $dbconn variable, which is the database connection handler and is required for many of the other functions.
17	Break out of the switch statement, since the case has been satisfied.
18–19	If none of the cases have been satisfied, then display a message that the $db value sent to the function was not valid.
20	Return 0 (false), so that any functions using this function know that the function failed.
21	End the switch statement.
22	End the function declaration.
24	Declare the selectDB function. The function requires the type of database ($db) as an argument.
25	Declare a global variable that can be accessed by this function. The variable is required to select the database.
26	Start a switch statement that checks to see which of the cases should be run, depending on the value of $db.
27	If $db = "psql", then the user wants to use a PostgreSQL database.
28	Return 1 (true), so that the function accessing this function knows that the call to the SelectDB function was successful. PostgreSQL syntax specifies which database to use during pg_connect(), which should have been run before this function.
29	Break out of the switch statement, since the case has been satisfied.
30	If $db = "mysql", then the user wants to use a MySQL database.
31	Execute the mysql_select_db() function to select the proper database on the MySQL server. If there is an error, then kill the script and provide an error message.
32	If there is not an error, then return 1 (true), so that the function accessing this function knows that the call to the SelectDB function was successful.
33	Break out of the switch statement, since the case has been satisfied.
34	If $db = "mssql", then the user wants to use a MS SQL database.
35	Execute the mssql_select_db() function to select the proper database on the MS SQL server. If there is an error, then kill the script and provide an error message.
36	If there is not an error, then return 1 (true), so that the function accessing this function knows that the call to the SelectDB function was successful.
37	Break out of the switch statement, since the case has been satisfied.
38–39	If none of the cases have been satisfied, then display a message that the $db value sent to the function was not valid.
40	Return 0 (false), so that any functions using this function know that the function failed.
41	End the switch statement.
42	End the function declaration.
44	Declare the queryDB function. The function requires the type of database ($db) and the SQL query ($query) as arguments.
45	Start a switch statement that checks to see which of the cases should be run, depending on the value of $db.
46	If $db = "psql", then the user wants to use a PostgreSQL database.
47	Run the query using pg_exec() and check if there is an error.
48	If there was an error, then set $result to 0.
49	End the if statement.
50	Break out of the switch statement, since the case has been satisfied.
51	If $db = "mysql", then the user wants to use a MySQL database.
52	Run the query using mysql_query() and check if there is an error.
53	If there was an error, then set $result to 0.
54	End the if statement.
55	Break out of the switch statement, since the case has been satisfied.
56	If $db = "mssql", then the user wants to use a MS SQL database.
57	Run the query using mssql_query() and check if there is an error.
58	If there was an error, then set $result to 0.
59	End the if statement.
60	Break out of the switch statement, since the case has been satisfied.
61–62	If none of the cases have been satisfied, then display a message that the $db value sent to the function was not valid.
63	Return 0 (false), so that any functions using this function know that the function failed.
64	End the switch statement.
65	Return the value of $result to the function calling this function. If the $result = 0, then the calling function knows an error has occurred.
66	End the function declaration.
68	Declare the returnDBarray function. The function requires the type of database ($db) and the result set from the previous query ($result) as arguments.
69	Verify that the result does not equal 0. If it does, then there was an error with the previous query. If there was no error, then continue.
70	Start a switch statement that checks to see which of the cases should be run, depending on the value of $db.
71	If $db = "psql", then the user wants to use a PostgreSQL database.
72	Fetch the array using pg_fetch_array() and check if there is an error.
73	If there was an error, then set $array to 0.
74	End the if statement.
75	Break out of the switch statement, since the case has been satisfied.
76	If $db = "mysql", then the user wants to use a MySQL database.
77	Fetch the array using mysql_fetch_array() and check if there is an error.
78	If there was an error, then set $array to 0.
79	End the if statement.
80	Break out of the switch statement, since the case has been satisfied.
81	If $db = "mssql", then the user wants to use a MS SQL database.
82	Fetch the array using mssql_fetch_array() and check if there is an error.
83	If there was an error, then set $array to 0.
84	End the if statement.
85	Break out of the switch statement, since the case has been satisfied.
86–87	If none of the cases have been satisfied, then display a message that the $db value sent to the function was not valid.
88	Set $array to 0 (false), so that any functions using this function know that the function failed.
89	End the switch statement.
90	Return the value of $result to the function calling this function. If the $result = 0, then the calling function knows an error has occurred.
91	End the if statement that checked to make sure that $result did not equal 0.
92	End the function declaration.
94	Declare the closeDB function. The function requires the type of database ($db) and the database connection ($dbconn) as arguments.
95	Start a switch statement that checks to see which of the cases should be run, depending on the value of $db.
96	If $db = "psql", then the user wants to use a PostgreSQL database.
97	Run pg_close() and check if there is an error.
98	If there was an error, then return 0, notifying the calling function that the close failed.
99–100	If there was not an error, then notify the calling function that the close succeeded.
101	End the if statement.
102	Break out of the switch statement, since the case has been satisfied.
103	If $db = "mysql", then the user wants to use a MySQL database.
104	Run mysql_close() and check if there is an error.
105	If there was an error, then return 0, notifying the calling function that the close failed.
106–107	If there was not an error, then notify the calling function that the close succeeded.
108	End the if statement.
109	Break out of the switch statement, since the case has been satisfied.
110	If $db = "mssql", then the user wants to use a MS SQL database.
111	Run mssql_close() and check if there is an error.
112	If there was an error, then return 0, notifying the calling function that the close failed.
113–114	If there was not an error, then notify the calling function that the close succeeded.
115	End the if statement.
116	Break out of the switch statement, since the case has been satisfied.
117–118	If none of the cases have been satisfied, then display a message that the $db value sent to the function was not valid.
119	Return 0 to notify the calling function that the function failed.
120	End the switch statement.
121	End the function declaration.
123	Declare the numrowsDB function. The function requires the type of database ($db) and the result set from the previous query ($result) as arguments.
124	Start a switch statement that checks to see which of the cases should be run, depending on the value of $db.
125	If $db = "psql", then the user wants to use a PostgreSQL database.
126	Run pg_numrows() and check if there is an error.
127	If there was an error, then return 0, notifying the calling function that the close failed.
128–129	If there was not an error, then notify the calling function that the close succeeded.
130	End the if statement.
131	Break out of the switch statement, since the case has been satisfied.
132	If $db = "mysql", then the user wants to use a MySQL database.
133	Run mysql_num_rows() and check if there is an error.
134	If there was an error, then return 0, notifying the calling function that the close failed.
135–136	If there was not an error, then notify the calling function that the close succeeded.
137	End the if statement.
138	Break out of the switch statement, since the case has been satisfied.
139	If $db = "mssql", then the user wants to use a MS SQL database.
140	Run mssql_num_rows() and check if there is an error.
141	If there was an error, then return 0, notifying the calling function that the close failed.
142–143	If there was not an error, then notify the calling function that the close succeeded.
144	End the if statement.
145	Break out of the switch statement, since the case has been satisfied.
146–147	If none of the cases have been satisfied, then display a message that the $db value sent to the function was not valid.
148	Return 0 to notify the calling function that the function failed.
149	End the switch statement.
150	End the function declaration.

The next part of the example is the SQL required to create the table for the sample application:

Script 3–3 addressbook.sql Script 3–4

1.  CREATE TABLE addressbook (
2.  first VARCHAR(32),
3.  last VARCHAR(32),
4.  home VARCHAR(16),
5.  cell VARCHAR(16),
6.  work VARCHAR(16));

The final bit is the example application, which uses the DBlib.php file as its database wrapper, allowing the application to be used with three different database back-ends without having to change any of the code. See Figure 3–2 for the output produced by this script:

FIGURE 3–2 customDB.php

Script 3–4 customDB.php Script 3–5

  1.  <?
  2.  $page = "customDB.php";
  3.
  4.  require_once("DBlib.php");
  5.  /* REQUIRED FOR DBlib.php */
  6.  //$db = "psql"; //PostgreSQL Database
  7.  //$db = "mysql"; //MySQL Database
  8.  $db = "mssql"; // MS SQL Database
  9.  $host = "192.168.0.1";
10.  $database = "php";
11.  $username = "mssqluser";
12.  $password = "password";
13.  /**************************/
14.
15.  function display_addresses ($db) {
16.      global $dbconn;
17.      selectDB($db, $dbconn);
18.      $sql = "select * from addressbook";
19.      if(!$result = queryDB($db, $sql)) {
20.          echo "<P>Error with query!";
21.      }
22.      $rows = numrowsDB($db, $result);
23.      if($rows == 0) {
24.          echo "There are entries in your addressbook.";
25.      } else {
26.      ?><table border=1><?
27.          while($row = returnDBarray($db, $result)) {
28.              ?>
29.              <tr><td colspan=2><b><?=$row['first'];?> <?=$row['last'];?></b></td></tr>
30.              <tr><td>Home: </td><td><?=$row['home'];?></td></tr>
31.              <tr><td>Cell: </td><td><?=$row['cell'];?></td></tr>
32.              <tr><td>Work: </td><td><?=$row['work'];?></td></tr>
33.              <?
34.          }
35.      ?></table><?
36.      }
37.  }
38.
39.  function add_address($db, $HTTP_POST_VARS) {
40.      global $dbconn;
41.      selectDB($db, $dbconn);
42.      $query = "insert into addressbook values ('" .
43.          $HTTP_POST_VARS['first'] . "','" .
44.          $HTTP_POST_VARS['last'] . "','" .
45.          $HTTP_POST_VARS['home'] . "','" .
46.          $HTTP_POST_VARS['cell'] . "','" .
47.          $HTTP_POST_VARS['work'] . "')";
48.      if(!queryDB($db, $query)) {
49.          echo $query;
50.          return 0;
51.      } else {
52.          return 1;
53.      }
54.  }
55.
56.  function add_address_form(){
57.      global $page;
58.      ?>
59.      <h3>Add An Address:</h3>
60.      <form action=<?=$page?> method=post>
61.      <p>First Name: <input type="text" name="first">
62.      <br>Last Name: <input type="text" name="last">
63.      <br>Home: <input type="text" name="home">
64.      <br>Cell: <input type="text" name="cell">
65.      <br>Work: <input type="text" name="work">
66.      <p><input type="submit" name="add_address" value="Add Entry!">
67.      </form>
68.      <?
69.  }
70.  /***** MAIN *****/
71.  ?>
72.  <h3>Address Book</h3>
73.  <p><a href=<?=$page?>?action=add>Add An Entry</a>
74.  <p>
75.  <?
76.  $dbconn = connectDB($db);
77.  if(isset($add_address)) {
78.      if(!add_address($db, $HTTP_POST_VARS)) {
79.          echo "<h3>ERROR ADDING ENTRY!</h3>";
80.      } else {
81.          echo "<h3>ENTRY ADDED!</h3>";
82.      }
83.  } elseif(isset($action) && $action == "add") {
84.      add_address_form();
85.  }
86.  ?>
87.  <h4>Current Addresses:</h4>
88.  <?
89.  display_addresses ($db);
90.  if(!closeDB($db, $dbconn)) {
91.      echo "<p>ERROR CLOSING DB CONNECTION";
92.  }
93.  ?>

Script 3–4 customDB.php Line-by-Line Explanation

LINE	DESCRIPTION
2	Declare the name of the page so that it can be used in a function that prints out a form action. This is useful when testing the script if you want to quickly give it a new name.
4	Require the DBlib.php file so that this script has access to the database wrapper.
6–8	The different databases that this script can access. Uncomment only one.
9–12	Database connection information required to connect to the database server and access the specific database.
15	Declare the display_addresses function. This function takes one argument, $db, which is defined above.
16	Make the $dbconn variable, the connection handler to the database, available to this function.
17	Run the selectDB function from DBlib.php.
18	Generate an SQL statement to select all of the entries in the address book table.
19	Query the database using the queryDB function from DBlib.php. If there is not an error, then $result should contain a valid database query result.
20	If there was an error, display an error message to the screen.
22	Execute the numrowsDB function from DBlb.php.
23–24	If there are no rows in the result set, then the database is empty. Notify the user that there are no entries in the address book.
25	If there are rows in the result set, then continue executing the function.
26	Create a table to display the results.
27	Loop through each row in the result set using the returnDBarray function from DBlib.php.
29–34	Display the data in the current row.
35	Close the table.
36	End the if statement started on line 23.
37	End the function declaration.
39	Declare the add_address function. It takes as arguments the database type ($db) and the variables sent from the add_address_form, which is defined later in the script.
40	Make the $dbconn variable accessible to this function.
41	Select the database using the selectDB function from DBlib.php.
42–47	Generate an SQL statement that inserts the data from the form into the database.
48–49	If the query fails, then echo the query to help debug.
50	Return 0, since the query failed.
51–53	If the query didn't fail, then return 1.
56–69	Declare a function that prints a standard form to the browser that allows the user to enter a new address book entry.
70	Start the main part of the script.
72	Print a heading for the page.
73	Create a link that, when clicked, displays the form so the user can add another entry.
76	Create a connection to the database using the connectDB function from DBlib.php.
77	If the $add_address variable is set, then run the add_address() function to add a new entry to the address book.
78–79	If the query fails, then print an error message.
80–82	If the query is successful, then print a message telling the user.
87	Print a heading for the current addresses in the database.
89	Run the display_addresses function to print out.
90	Close the database connection using the closeDB function fromDBlib.php.
91	If there is an error closing the database connection, then notify the user.
92	End the if statement that began on line 77.

< Back Page 4 of 5 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

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

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about 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 information@informit.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 InformIT. 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.informit.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

Email Address