pike.git / lib / modules / Sql.pmod / pgsql.pike

version» Context lines:

pike.git/lib/modules/Sql.pmod/pgsql.pike:223:      //! @returns   //! The textual description of the last   //! server-related error. Returns @expr{0@} if no error has occurred   //! yet. It is not cleared upon reading (can be invoked multiple   //! times, will return the same result until a new error occurs).   //!   //! During the execution of a statement, this function accumulates all   //! non-error messages (notices, warnings, etc.). If a statement does not   //! generate any errors, this function will return all collected messages - //! from the last statement. + //! since the last statement.   //!   //! @note   //! The string returned is not newline-terminated.   //!   //! @param clear   //! To clear the error, set it to @expr{1@}.   //!   //! @seealso   //! @[big_query()]   /*semi*/final string error(void|int clear) {
pike.git/lib/modules/Sql.pmod/pgsql.pike:1696:   //! Forces caching on or off for the query at hand.   //! @member int ":_text"   //! Forces text mode in communication with the database for queries on or off   //! for the query at hand. Potentially more efficient than the default   //! binary method for simple queries with small or no result sets.   //! Note that this mode causes all but the first query result of a list   //! of semicolon separated statements to be discarded.   //! @member int ":_sync"   //! Forces synchronous parsing on or off for statements.   //! Setting this to off can cause surprises because statements could - //! be parsed before the previous statements have been executed. - //! This can speed up parsing by increased parallelism. + //! be parsed before the previous statements have been executed + //! (e.g. references to temporary tables created in the preceding + //! statement), + //! but it can speed up parsing due to increased parallelism.   //! @endmapping   //!   //! @note   //! The bindings-parameter passed to this function must remain unaltered   //! until the parameters have been sent to the database. The driver   //! currently does not expose this moment, but to avoid a race condition   //! it is sufficient to keep them unaltered until the first resultrow   //! has been fetched (or EOF is reached, in case of no resultrows).   //!   //! @returns