pike.git
/
lib
/
modules
/
Sql.pmod
/
pgsql.pike
version
»
Context lines:
10
20
40
80
file
none
3
pike.git/lib/modules/Sql.pmod/pgsql.pike:182:
//! @member int force_ssl //! If the database supports and allows SSL connections, the session //! will be SSL encrypted, if not, the connection will abort //! @member int cache_autoprepared_statements //! If set to zero, it disables the automatic statement prepare and //! cache logic; caching prepared statements can be problematic //! when stored procedures and tables are redefined which leave stale //! references in the already cached prepared statements //! @member string client_encoding //! Character encoding for the client side, it defaults to using
-
//! the default encoding specified by the database, e.g.
:
"SQL
_
ASCII"
+
//! the default encoding specified by the database, e.g.
+
//!
@ref{UTF8@} or @ref{SQL
_
ASCII@}.
//! @member string standard_conforming_strings //! When on, backslashes in strings must not be escaped any longer, //! @[quote()] automatically adjusts quoting strategy accordingly //! @member string escape_string_warning //! When on, a warning is issued if a backslash (\) appears in an //! ordinary string literal and @[standard_conforming_strings] is off, //! defaults to on //! @endmapping //! For the numerous other options please check the PostgreSQL manual. //!
pike.git/lib/modules/Sql.pmod/pgsql.pike:344:
{ return _runtimeparameter[CLIENT_ENCODING]; } //! @returns //! Currently active runtimeparameters for //! the open session; these are initialised by the @ref{options@} parameter //! during session creation, and then processed and returned by the server. //! Common values are: //! @mapping //! @member string client_encoding
-
//! Character encoding for the client side, e.g.
:
"SQL
_
ASCII"
+
//! Character encoding for the client side, e.g.
+
//!
@ref{UTF8@} or @ref{SQL
_
ASCII@}.
//! @member string server_encoding //! Character encoding for the server side as determined when the
-
//! database was created, e.g.
:
"SQL
_
ASCII"
+
//! database was created, e.g.
@ref{UTF8@} or @ref{SQL
_
ASCII@}
//! @member string DateStyle
-
//! Date parsing/display, e.g.
:
"ISO
,
DMY"
+
//! Date parsing/display, e.g.
@ref{ISO
,
DMY@}
//! @member string TimeZone
-
//! Default timezone used by the database, e.g.
:
"localtime"
+
//! Default timezone used by the database, e.g.
@ref{localtime@}
//! @member string standard_conforming_strings //! When on, backslashes in strings must not be escaped any longer //! @member string session_authorization //! Displays the authorisationrole which the current session runs under //! @member string is_superuser //! Indicates if the current authorisationrole has database-superuser //! privileges //! @member string integer_datetimes //! Reports wether the database supports 64-bit-integer dates and times //! @member string server_version
-
//! Shows the server version, e.g.
:
"8
.3.
3"
+
//! Shows the server version, e.g.
@ref{8
.3.
3@}
//! @endmapping //! //! The values can be changed during a session using SET commands to the //! database. //! For other runtimeparameters check the PostgreSQL documentation. //! //! @seealso //! @url{http://search.postgresql.org/search?u=%2Fdocs%2F&q=client+connection+defaults@} //! //! @note
pike.git/lib/modules/Sql.pmod/pgsql.pike:1555:
//! @decl Sql.pgsql_util.pgsql_result big_query(string query) //! @decl Sql.pgsql_util.pgsql_result big_query(string query, mapping bindings) //! //! This is the only provided interface which allows you to query the //! database. If you wish to use the simpler @[Sql.Sql()->query()] function, //! you need to use the @[Sql.Sql] generic SQL-object. //! //! Bindings are supported natively straight across the network. //! Special bindings supported are: //! @mapping
-
//! @member int
"
:_cache
"
+
//! @member int :_cache
//! Forces caching on or off for the query at hand. //! @endmapping //! //! @returns //! A @[Sql.pgsql_util.pgsql_result] object (which conforms to the //! @[Sql.sql_result] standard interface for accessing data). It is //! recommended to use @[Sql.Sql()->query()] for simpler queries (because //! it is easier to handle, but stores all the result in memory), and //! @[Sql.Sql()->big_query()] for queries you expect to return huge amounts of //! data (it's harder to handle, but fetches results on demand).