Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /usr/share/php/PhpDocumentor/phpDocumentor/Smarty-2.6.0/libs/Smarty_Compiler.class.php on line 370
AwlDBDialectThe AwlDBDialect class handles support for different SQL dialects
This subpackage provides dialect specific support for PostgreSQL, and may, over time, be extended to provide support for other SQL dialects.
If you are looking for the place to add support for other SQL dialects, this is the class that you should be looking at. You might also look at the AwlDatabase class which extends this one, but these are the core capabilities which most probably need attention.
Located in /AwlDBDialect.php (line 33)
| Class | Description |
|---|---|
AwlDatabase
|
Typically there will only be a single instance of the database level class in an application. |
AwlDBDialect
__construct
(string $connection_string, [string $dbuser = null], [string $dbpass = null], [array $options = null])
mixed
$db
(line 46)
Holds the PDO database connection
mixed
$dialect
(line 41)
Holds the name of the database dialect
Constructor __construct (line 68)
Parses the connection string to ascertain the database dialect. Returns true if the dialect is supported and fails if the dialect is not supported. All code to support any given database should be within in an external include.
The database will be opened.
GetFields (line 138)
Returns the SQL for the current database dialect which will return a two-column resultset containing a list of fields and their associated data types.
GetVersion (line 109)
Sets the current search path for the database.
Quote (line 182)
Returns $value escaped in an appropriate way for this database dialect.
ReplaceNamedParameters (line 340)
Replaces named query parameters of the form :name with appropriately escaped substitutions.
The function takes a variable number of arguments, the first is the SQL string, with replaceable ':name' characters (a la DBI). The subsequent parameters being the values to replace into the SQL string.
The values passed to the routine are analyzed for type, and quoted if they appear to need quoting. This can go wrong for (e.g.) NULL or other special SQL values which are not straightforwardly identifiable as needing quoting (or not).
ReplaceParameters (line 284)
Replaces query parameters with appropriately escaped substitutions.
The function takes a variable number of arguments, the first is the SQL string, with replaceable '?' characters (a la DBI). The subsequent parameters being the values to replace into the SQL string.
The values passed to the routine are analyzed for type, and quoted if they appear to need quoting. This can go wrong for (e.g.) NULL or other special SQL values which are not straightforwardly identifiable as needing quoting (or not). In such cases the parameter can be forced to be inserted unquoted by passing it as "array( 'plain' => $param )".
SetSearchPath (line 91)
Sets the current search path for the database.
TranslateSQL (line 168)
Translates the given SQL string into a form that will hopefully work for this database dialect. This hook is intended to be used by developers to provide support for differences in database operation by translating the query string in an arbitrary way, such as through a file or database lookup.
The actual translation to other SQL dialects will be application-specific, so that any routines called by this will be external to this library, or will use resources loaded from some source external to this library.
The application developer is expected to use this functionality to solve harder translation problems, but is less likely to call this directly, hopefully switching ->Prepare to ->PrepareTranslated in those cases, and then adding that statement to whatever SQL translation infrastructure is in place.
Documentation generated on Wed, 04 Jul 2012 07:06:12 +0000 by phpDocumentor 1.4.3