П О Р Т А Л                            
С Е Т Е В Ы Х                          
П Р О Е К Т О В                        
Поиск по сайту:

О проекте

     HTML & JavaScript
     XML & XSLT
     Unix Shell





Самое читаемое:

Учебник PHP - "Для Чайника".
Просмотров 162 раз(а).

Иллюстрированный самоучитель по созданию сайтов.
Просмотров 92993 раз(а).

Учебник HTML.
Просмотров 81553 раз(а).

Руководство по PHP5.
Просмотров 51910 раз(а).

Хостинг через призму DNS.
Просмотров 60357 раз(а).

Подборка текстов стандартных документов.
Просмотров 50533 раз(а).

Учебник PHP - Самоучитель
Просмотров 57875 раз(а).

Документация на MySQL (учебник & справочное руководство)
Просмотров 59376 раз(а).

Внешние атаки...
Просмотров 48919 раз(а).

Учебник PHP.
Просмотров 42423 раз(а).

SSI в примерах.
Просмотров 32717 раз(а).

| Добавить в избранное | Сделать стартовой | Помощь

Руководство по PHP
Пред. Глава 45. PDO Driver How-To След.

Error handling

Error handling is implemented using a hand-shaking protocol between PDO and the database driver code. The database driver code signals PDO than an error has occurred via a failure (0) return from any of the interface functions. If a zero is returned, the field error_code in the control block appropriate to the context (either the pdo_dbh_t or pdo_stmt_t block). In practice, it is probably a good idea to set the field in both blocks to the same value to ensure the correct one is getting used.

The error_mode field is a six-byte field containing a 5 character ASCIIZ SQLSTATE identifier code. This code drives the error message process. The SQLSTATE code is used to look up an error message in the internal PDO error message table (see pdo_sqlstate.c for a list of error codes and their messages). If the code is not known to PDO, a default "Unknown Message" value will be used.

In addition to the SQLSTATE code and error message, PDO will call the driver-specific fetch_err() routine to obtain supplemental data for the particular error condition. This routine is passed an array into which the driver may place additional information. This array has slot positions assigned to particular types of supplemental info:

  1. A native error code. This will frequently be an error code obtained from the database API.

  2. A descriptive string. This string can contain anything additional information related to the failure. Database drivers typically include information such as an error message, code location of the failure, and any additional descriptive information the driver developer feels worthy of inclusion. It is generally a good idea to include all diagnostic information obtainable from the database interface at the time of the failure. For driver-detected errors (such as memory allocation problems), the driver developer can define whatever error information that seems appropriate.

Пред. Начало След.
Constants Уровень выше Zend API: Hacking the Core of PHP

Если Вы не нашли что искали, то рекомендую воспользоваться поиском по сайту:

Copyright © 2005-2016 Project.Net.Ru