CXI. PostgreSQL 数据库函数

简介

PostgreSQL 是一个开放源码的免费数据库系统。Postgres 最初由加州大学伯克利分校计算机科学系开发，倡导了很多关系对象的观念，这些观念现在已经用在一些商业数据库系统中。它提供了 SQL92/SQL99 语言支持，事务处理，引用集成，存储过程以及类型扩展。PostgreSQL 则是 Postgres 的一个开放源代码的后代。

需求

要使用 PostgreSQL 支持，需要 PostgreSQL 6.5 或更新版本，PostgreSQL 8.0 或更新版本来使用所有的 PostgreSQL 模块。PostgreSQL 支持多种字符编码包括多字节字符编码。关于 PostgreSQL 的当前版本以及更多信息见 http://www.postgresql.org/ 以及 PostgreSQL 文档。

安装

为添加 PostgreSQL 支持，在编译 PHP 时需要加上 --with-pgsql[=DIR] 选项。如果可以用共享模块方式，PostgreSQL 模块可以在 php.ini 用 extension 指令或者 dl() 函数加载。

运行时配置

这些函数的行为受 php.ini 的影响。

表格 1. PostgreSQL 配置选项

名称	默认值	可变范围	更新日志
pgsql.allow_persistent	"1"	PHP_INI_SYSTEM
pgsql.max_persistent	"-1"	PHP_INI_SYSTEM
pgsql.max_links	"-1"	PHP_INI_SYSTEM
pgsql.auto_reset_persistent	"0"	PHP_INI_SYSTEM	从 PHP 4.2.0 起开始存在
pgsql.ignore_notice	"0"	PHP_INI_ALL	从 PHP 4.3.0 起开始存在
pgsql.log_notice	"0"	PHP_INI_ALL	从 PHP 4.3.0 起开始存在

有关 PHP_INI_* 常量进一步的细节与定义参见附录 G。

以下是配置选项的简要解释。

pgsql.allow_persistent boolean: 是否允许持久的 Postgres 连接。
pgsql.max_persistent integer: 每个进程所能有的持久 Postgres 连接数目。
pgsql.max_links integer: 每个进程所能有的 Postgres 连接数目，包括持久连接。
pgsql.auto_reset_persistent integer: 检测用在 pg_pconnect() 上的中断了的持久连接。需要一些损耗。
pgsql.ignore_notice integer: 是否忽略 PostgreSQL 后端的通告。
pgsql.log_notice integer: 是否记录 PostgreSQL 后端的通告消息。要记录通告消息日志，PHP 指令 pgsql.ignore_notice 必须为 off。

资源类型

PostgreSQL 模块使用了两种资源类型。第一种是数据库连接的标识符，第二种是保存查询结果的资源。

预定义常量

以下常量由本扩展模块定义，因此只有在本扩展模块被编译到 PHP 中，或者在运行时被动态加载后才有效。

PGSQL_ASSOC (integer): Passed to pg_fetch_array(). Return an associative array of field names and values.
PGSQL_NUM (integer): Passed to pg_fetch_array(). Return a numerically indexed array of field numbers and values.
PGSQL_BOTH (integer): Passed to pg_fetch_array(). Return an array of field values that is both numerically indexed (by field number) and associated (by field name).
PGSQL_CONNECT_FORCE_NEW (integer): Passed to pg_connect() to force the creation of a new connection, rather then re-using an existing identical connection.
PGSQL_CONNECTION_BAD (integer): Returned by pg_connection_status() indicating that the database connection is in an invalid state.
PGSQL_CONNECTION_OK (integer): Returned by pg_connection_status() indicating that the database connection is in a valid state.
PGSQL_SEEK_SET (integer): Passed to pg_lo_seek(). Seek operation is to begin from the start of the object.
PGSQL_SEEK_CUR (integer): Passed to pg_lo_seek(). Seek operation is to begin from the current position.
PGSQL_SEEK_END (integer): Passed to pg_lo_seek(). Seek operation is to begin from the end of the object.
PGSQL_EMPTY_QUERY (integer): Returned by pg_result_status(). The string sent to the server was empty.
PGSQL_COMMAND_OK (integer): Returned by pg_result_status(). Successful completion of a command returning no data.
PGSQL_TUPLES_OK (integer): Returned by pg_result_status(). Successful completion of a command returning data (such as a SELECT or SHOW).
PGSQL_COPY_OUT (integer): Returned by pg_result_status(). Copy Out (from server) data transfer started.
PGSQL_COPY_IN (integer): Returned by pg_result_status(). Copy In (to server) data transfer started.
PGSQL_BAD_RESPONSE (integer): Returned by pg_result_status(). The server's response was not understood.
PGSQL_NONFATAL_ERROR (integer): Returned by pg_result_status(). A nonfatal error (a notice or warning) occurred.
PGSQL_FATAL_ERROR (integer): Returned by pg_result_status(). A fatal error occurred.
PGSQL_TRANSACTION_IDLE (integer): Returned by pg_transaction_status(). Connection is currently idle, not in a transaction.
PGSQL_TRANSACTION_ACTIVE (integer): Returned by pg_transaction_status(). A command is in progress on the connection. A query has been sent via the connection and not yet completed.
PGSQL_TRANSACTION_INTRANS (integer): Returned by pg_transaction_status(). The connection is idle, in a transaction block.
PGSQL_TRANSACTION_INERROR (integer): Returned by pg_transaction_status(). The connection is idle, in a failed transaction block.
PGSQL_TRANSACTION_UNKNOWN (integer): Returned by pg_transaction_status(). The connection is bad.
PGSQL_DIAG_SEVERITY (integer): Passed to pg_result_error_field(). The severity; the field contents are ERROR, FATAL, or PANIC (in an error message), or WARNING, NOTICE, DEBUG, INFO, or LOG (in a notice message), or a localized translation of one of these. Always present.
PGSQL_DIAG_SQLSTATE (integer): Passed to pg_result_error_field(). The SQLSTATE code for the error. The SQLSTATE code identifies the type of error that has occurred; it can be used by front-end applications to perform specific operations (such as error handling) in response to a particular database error. This field is not localizable, and is always present.
PGSQL_DIAG_MESSAGE_PRIMARY (integer): Passed to pg_result_error_field(). The primary human-readable error message (typically one line). Always present.
PGSQL_DIAG_MESSAGE_DETAIL (integer): Passed to pg_result_error_field(). Detail: an optional secondary error message carrying more detail about the problem. May run to multiple lines.
PGSQL_DIAG_MESSAGE_HINT (integer): Passed to pg_result_error_field(). Hint: an optional suggestion what to do about the problem. This is intended to differ from detail in that it offers advice (potentially inappropriate) rather than hard facts. May run to multiple lines.
PGSQL_DIAG_STATEMENT_POSITION (integer): Passed to pg_result_error_field(). A string containing a decimal integer indicating an error cursor position as an index into the original statement string. The first character has index 1, and positions are measured in characters not bytes.
PGSQL_DIAG_INTERNAL_POSITION (integer): Passed to pg_result_error_field(). This is defined the same as the PG_DIAG_STATEMENT_POSITION field, but it is used when the cursor position refers to an internally generated command rather than the one submitted by the client. The PG_DIAG_INTERNAL_QUERY field will always appear when this field appears.
PGSQL_DIAG_INTERNAL_QUERY (integer): Passed to pg_result_error_field(). The text of a failed internally-generated command. This could be, for example, a SQL query issued by a PL/pgSQL function.
PGSQL_DIAG_CONTEXT (integer): Passed to pg_result_error_field(). An indication of the context in which the error occurred. Presently this includes a call stack traceback of active procedural language functions and internally-generated queries. The trace is one entry per line, most recent first.
PGSQL_DIAG_SOURCE_FILE (integer): Passed to pg_result_error_field(). The file name of the PostgreSQL source-code location where the error was reported.
PGSQL_DIAG_SOURCE_LINE (integer): Passed to pg_result_error_field(). The line number of the PostgreSQL source-code location where the error was reported.
PGSQL_DIAG_SOURCE_FUNCTION (integer): Passed to pg_result_error_field(). The name of the PostgreSQL source-code function reporting the error.
PGSQL_ERRORS_TERSE (integer): Passed to pg_set_error_verbosity(). Specified that returned messages include severity, primary text, and position only; this will normally fit on a single line.
PGSQL_ERRORS_DEFAULT (integer): Passed to pg_set_error_verbosity(). The default mode produces messages that include the above plus any detail, hint, or context fields (these may span multiple lines).
PGSQL_ERRORS_VERBOSE (integer): Passed to pg_set_error_verbosity(). The verbose mode includes all available fields.
PGSQL_STATUS_LONG (integer): Passed to pg_result_status(). Indicates that numerical result code is desired.
PGSQL_STATUS_STRING (integer): Passed to pg_result_status(). Indicates that textual result command tag is desired.
PGSQL_CONV_IGNORE_DEFAULT (integer): Passed to pg_convert(). Ignore default values in the table during conversion.
PGSQL_CONV_FORCE_NULL (integer): Passed to pg_convert(). Use SQL NULL in place of an empty string.
PGSQL_CONV_IGNORE_DEFAULT (integer): Passed to pg_convert(). Ignore conversion of NULL into SQL NOT NULL columns.

注释

注: 不是所有的版本都支持所有的函数，这和 libpq（PostgreSQL C 客户端库）的版本和编译方法有关。如果 PHP 的 PostgreSQL 扩展不见了，那是因为 libpq 的版本不支持它。

注: 大多数 PostgreSQL 函数接受 connection 作为第一个可选参数。如果没有提供，则使用上一个打开的连接。如果没有打开的连接，函数返回 FALSE。

注: PostgreSQL 在创建对象和查询时自动将所有标识符（例如表／列名）转成小写字母值。要强制其使用混合或大写字母的标识符，必须将标识符用双引号（"）转义。

注: PostgreSQL 没有特殊的命令来取得数据库的结构信息（例如当前数据库中的所有表）。不过在 PostgreSQL 7.4 及以上版本有一个标准结构名叫 information_schema，它包含有系统视图以及所有必要的信息，可以很容易地查询出来。其细节见 PostgreSQL 文档。

范例

此简单例子演示了 PostgreSQL 数据库的连接，执行查询，显示结果以及断开连接。
例子 1. PostgreSQL 例子
<?php // 连接，选择数据库 $db = pg_connect("host=localhost dbname=publishing user=www password=foo"); or die('Could not connect: ' . pg_last_error()); // 执行 SQL 查询 $query = 'SELECT * FROM authors'; $result = pg_query($query) or die('Query failed: ' . pg_last_error()); // 用 HTML 显示结果 echo "<table>\n"; while ($line = pg_fetch_array($result, null, PGSQL_ASSOC)) { echo "\t<tr>\n"; foreach ($line as $col_value) { echo "\t\t<td>$col_value</td>\n"; } echo "\t</tr>\n"; } echo "</table>\n"; // 释放结果集 pg_free_result($result); // 关闭连接 pg_close($link); ?>

目录
pg_affected_rows -- 返回受影响的记录数目
pg_cancel_query -- 取消异步查询
pg_client_encoding -- 取得客户端编码方式
pg_close -- 关闭一个 PostgreSQL 连接
pg_connect -- 打开一个 PostgreSQL 连接
pg_connection_busy -- 获知连接是否为忙
pg_connection_reset -- 重置连接（再次连接）
pg_connection_status -- 获得连接状态
pg_convert -- 将关联的数组值转换为适合 SQL 语句的格式。
pg_copy_from -- 根据数组将记录插入表中
pg_copy_to -- 将一个表拷贝到数组中
pg_dbname -- 获得数据库名
pg_delete -- 删除记录
pg_end_copy -- 与 PostgreSQL 后端同步
pg_escape_bytea -- 转义 bytea 类型的二进制数据
pg_escape_string -- 转义 text/char 类型的字符串
pg_execute -- Sends a request to execute a prepared statement with given parameters, and waits for the result.
pg_fetch_all_columns -- Fetches all rows in a particular result column as an array
pg_fetch_all -- 从结果中提取所有行作为一个数组
pg_fetch_array -- 提取一行作为数组
pg_fetch_assoc -- 提取一行作为关联数组
pg_fetch_object -- 提取一行作为对象
pg_fetch_result -- 从结果资源中返回值
pg_fetch_row -- 提取一行作为枚举数组
pg_field_is_null -- 测试字段是否为 NULL
pg_field_name -- 返回字段的名字
pg_field_num -- 返回字段的编号
pg_field_prtlen -- 返回打印出来的长度
pg_field_size -- 返回指定字段占用内部存储空间的大小
pg_field_type_oid -- Returns the type ID (OID) for the corresponding field number
pg_field_type -- 返回相应字段的类型名称
pg_free_result -- 释放查询结果占用的内存
pg_get_notify -- Ping 数据库连接
pg_get_pid -- Ping 数据库连接
pg_get_result -- 取得异步查询结果
pg_host -- 返回和某连接关联的主机名
pg_insert -- 将数组插入到表中
pg_last_error -- 得到某连接的最后一条错误信息
pg_last_notice -- 返回 PostgreSQL 服务器最新一条公告信息
pg_last_oid -- 返回上一个对象的 oid
pg_lo_close -- 关闭一个大型对象
pg_lo_create -- 新建一个大型对象
pg_lo_export -- 将大型对象导出到文件
pg_lo_import -- 将文件导入为大型对象
pg_lo_open -- 打开一个大型对象
pg_lo_read_all -- 读入整个大型对象并直接发送给浏览器
pg_lo_read -- 从大型对象中读入数据
pg_lo_seek -- 移动大型对象中的指针
pg_lo_tell -- 返回大型对象的当前指针位置
pg_lo_unlink -- 删除一个大型对象
pg_lo_write -- 向大型对象写入数据
pg_meta_data -- 获得表的元数据
pg_num_fields -- 返回字段的数目
pg_num_rows -- 返回行的数目
pg_options -- 获得和连接有关的选项
pg_parameter_status -- Looks up a current parameter setting of the server.
pg_pconnect -- 打开一个持久的 PostgreSQL 连接
pg_ping -- Ping 数据库连接
pg_port -- 返回该连接的端口号
pg_prepare -- Submits a request to create a prepared statement with the given parameters, and waits for completion.
pg_put_line -- 向 PostgreSQL 后端发送以 NULL 结尾的字符串
pg_query_params -- Submits a command to the server and waits for the result, with the ability to pass parameters separately from the SQL command text.
pg_query -- 执行查询
pg_result_error_field -- Returns an individual field of an error report.
pg_result_error -- 获得查询结果的错误信息
pg_result_seek -- 在结果资源中设定内部行偏移量
pg_result_status -- 获得查询结果的状态
pg_select -- 选择记录
pg_send_execute -- Sends a request to execute a prepared statement with given parameters, without waiting for the result(s).
pg_send_prepare -- Sends a request to create a prepared statement with the given parameters, without waiting for completion.
pg_send_query_params -- Submits a command and separate parameters to the server without waiting for the result(s).
pg_send_query -- 发送异步查询
pg_set_client_encoding -- 设定客户端编码
pg_set_error_verbosity -- Determines the verbosity of messages returned by pg_last_error() and pg_result_error().
pg_trace -- 启动一个 PostgreSQL 连接的追踪功能
pg_transaction_status -- Returns the current in-transaction status of the server.
pg_tty -- 返回该连接的 tty 号
pg_unescape_bytea -- 取消 bytea 类型中的字符串转义
pg_untrace -- 关闭 PostgreSQL 连接的追踪功能
pg_update -- 更新表
pg_version -- Returns an array with client, protocol and server version (when available)

add a note User Contributed Notes

21-Oct-2006 01:10


Lots of advice on stored procedures didn't work for me.  This did:



<?php

$response = pg_query( $connection, "BEGIN; DECLARE s CURSOR FOR SELECT get_consumer('harry'); FETCH ALL IN s; END;" );

?>



..where harry looks like this:



CREATE OR REPLACE FUNCTION get_consumer( varchar )

RETURNS refcursor

AS '

DECLARE

  _name          ALIAS FOR $1;

  r              refcursor;

BEGIN

  OPEN r FOR SELECT name FROM consumer

  WHERE

    consumer.name = _name

  ;

  RETURN r;

END

' LANGUAGE 'plpgsql';

Chris KL
11-Nov-2005 09:17


Here is a better array parser for PHP.  It will work with 1-d arrays only.  Unlike the example below it will work in all cases.



    /**

     * Change a db array into a PHP array

     * @param $arr String representing the DB array

     * @return A PHP array

     */

    function phpArray($dbarr) {

        // Take off the first and last characters (the braces)

        $arr = substr($dbarr, 1, strlen($dbarr) - 2);



        // Pick out array entries by carefully parsing.  This is necessary in order

        // to cope with double quotes and commas, etc.

        $elements = array();

        $i = $j = 0;        

        $in_quotes = false;

        while ($i < strlen($arr)) {

            // If current char is a double quote and it's not escaped, then

            // enter quoted bit

            $char = substr($arr, $i, 1);

            if ($char == '"' && ($i == 0 || substr($arr, $i - 1, 1) != '\\')) 

                $in_quotes = !$in_quotes;

            elseif ($char == ',' && !$in_quotes) {

                // Add text so far to the array

                $elements[] = substr($arr, $j, $i - $j);

                $j = $i + 1;

            }

            $i++;

        }

        // Add final text to the array

        $elements[] = substr($arr, $j);



        // Do one further loop over the elements array to remote double quoting

        // and escaping of double quotes and backslashes

        for ($i = 0; $i < sizeof($elements); $i++) {

            $v = $elements[$i];

            if (strpos($v, '"') === 0) {

                $v = substr($v, 1, strlen($v) - 2);

                $v = str_replace('\\"', '"', $v);

                $v = str_replace('\\\\', '\\', $v);

                $elements[$i] = $v;

            }

        }



        return $elements;

    }

1413 at blargh dot com
12-Oct-2005 08:09


Here is some quick and dirty code to convert Postgres-returned arrays into PHP arrays.  There's probably a billion bugs, but since I'm only dealing with variable-depth-and-length arrays of integers, it works for my needs.



Most notably, any data that might have commas in it won't work right...



<?php

function PGArrayToPHPArray($pgArray)

{

  $ret = array();

  $stack = array(&$ret);

  $pgArray = substr($pgArray, 1, -1);

  $pgElements = explode(",", $pgArray);

  

  ArrayDump($pgElements);



  foreach($pgElements as $elem)

    {

      if(substr($elem,-1) == "}")

        {

          $elem = substr($elem,0,-1);

          $newSub = array();

          while(substr($elem,0,1) != "{")

            {

              $newSub[] = $elem;

              $elem = array_pop($ret);

            }

          $newSub[] = substr($elem,1);

          $ret[] = array_reverse($newSub);

        }

      else

        $ret[] = $elem;

    }

  return $ret;

}

?>

anis_wn at gawab dot com
06-Jun-2005 12:45


Setting up PostgreSQL for higher security PHP connection.



Case:

We want to connect to PostgreSQL database using username and password supplied by webuser at login time.



Fact (Linux):

Apache (perhaps other servers, too) running the server as (default to) apache user account. So if you connect to PostgreSQL using default user, apache will be assingned for it. If you hard code the user and password in your PHP script, you'll loose security restriction from PostgreSQL.



Solution:

(You are assumed to have enough privilege to do these things, though)

1. Edit pg_hba.conf to have the line like the one below

    host    db_Name    [web_server_ip_address] [ip_address_mask] md5

2. Add to you script the login page that submits username and password.

3. Use those information to login to PostgreSQL like these...

<?

    $conn = "host=$DBHost port=$DBPort dbname=$DBName ".

            "user='{$_POST['dbUsername']}' password='{$_POST['dbPassword']}'";

    $db = pg_connect ($conn);

[your other codes go here...]

?>

4. You must add users in PostgreSQL properly.

5. For your convenience, you can store the username and password to $_SESSION variable.



Good luck.

Anis WN

WillowCatkin at hotmail dot com
21-May-2005 09:43


There is an example:

<?php

/*

 * Define PostgreSQL database server connect parameters.

 */

define('PGHOST','10.0.0.218');

define('PGPORT',5432);

define('PGDATABASE','example');

define('PGUSER', 'root');

define('PGPASSWORD', 'nopass');

define('PGCLIENTENCODING','UNICODE');

define('ERROR_ON_CONNECT_FAILED','Sorry, can not connect the database server now!');



/*

 * Merge connect string and connect db server with default parameters.

 */

pg_pconnect('host=' . PGHOST . ' port=' . PGPORT . ' dbname=' . PGDATABASE . ' user=' . PGUSER . ' password=' . PGPASSWORD);



/*

 * generate sql statements to call db-server-side stored procedure(or function) 

 * @parameter    string    $proc        stored procedure name.

 * @parameter    array    $paras        parameters, 2 dimensions array.

 * @return        string    $sql = 'select "proc"(para1,para2,para3);'

 * @example    pg_prepare('userExists',

 *                            array(

 *                                array('userName','chin','string'),

 *                                array('userId','7777','numeric')

 *                            )

 * )

 */

function pg_prepare($proc, $paras)

{

    $sql = 'select "' . $proc . '"(';

    $sql .= $paras[0][2] == 'numeric' ? $paras[0][1] : "'" . str_replace("'","''",$paras[0][1]) . "'";

    $len = count($paras);

    for ($i = 1; $i < $len; $i ++)

    {

        $sql .= ',';

        $sql .= $paras[$i][2] == 'numeric' ? $paras[$i][1] : "'" . str_replace("'","''",$paras[$i][1]) . "'";

    }

    $sql .= ');';

    return $sql;

}

?>

adaml at mimuw edu pl
02-Oct-2004 09:07


Yes, PHP does support stored procedures

You have to add "select" before the name of the 

procedure, just like that:



$result = pg_querry($conn, "SELECT procedure_x($aa)");



if a procedure returns a cursor you do something like that:



$result = pg_query($conn, "SELECT procedure_x('rcursor'); FETCH ALL IN rcursor");

raja shahed at christine nothdurfter dot com
17-Jul-2004 02:14


A very good tutorial for Windows users' is here http://www.sitepoint.com/article/use-postgresql-php-windows. Herr Johan Faxer Shows also how to install Cygwin.

74012 dot 2773 at compuserve dot com
02-Jul-2004 12:35


for just a list of tables, this works with postgresql-7.2.1:



function pg_list_tables($db) {

    $sql = "select relname from pg_stat_user_tables order by relname;";

    return pg_query($db, $sql);

}

abondi at ijk dot it
26-May-2004 08:11


I've found another function to mimic the following mysql list tables function (http://www.php.net/manual/en/function.mysql-list-tables.php) that's more useful for my target:



function pg_list_tables() {

      $sql = "SELECT a.relname AS Name

          FROM pg_class a, pg_user b

          WHERE ( relkind = 'r') and relname !~ '^pg_' AND relname !~ '^sql_'

          AND relname !~ '^xin[vx][0-9]+' AND b.usesysid = a.relowner

          AND NOT (EXISTS (SELECT viewname FROM pg_views WHERE viewname=a.relname));";

      return(pg_query($conn, $sql));

}

fmonteiro11 at hotmail dot com
16-Jan-2004 02:50


Another good source of knowledge is http://www.faqs.org/docs/ppbook/book1.htm

daniel at bichara dot com dot br
31-Dec-2002 09:04


Running RedHat Linux and Apache with suexec enabled you must include pgsql.so on each .php file using dl("pgsql.so") and remove "extension=pgsql.so" from php.ini, otherwise Apache (httpd) will not start.

anonymous at unknown dot com
30-Nov-2002 01:50


I just wanted to add to my previous post I've got the system up and running.

Environment: Windows XP, Apache 1.3.23, Php 4.3 RC2, PostGreSQL beta4 native windows build



Installation was fairly easy: 

1. read the readme.txt

2. edit the setenv.bat as described in readme

3. run 'initdb'

    all execs are in /bin

    help is accessed like <command> --help

4. Start the psql deamon - you may want to create a batch file like

    'D:\postgres_beta4\bin\postmaster -h localhost -D D:/postgres_beta4/data'



    --deamon should be up and running now--



You can login into a shell from a console like

    'psql -h localhost -d <username>'



You must load the postgresql extension by editing the php.ini and restarting apache in order to access psql with php.



And one final not: when running

    $dbconn = pg_connect ("host=localhost port=5432 dbname=$dbname user=$user");

remember that $user and or $dbname is CASESENSITIVE.



Oh yeah, I created the data dir manually - don't know whether that was necessary



Grtz Vargo

swm at php dot net
22-Aug-2002 11:49


My talk on PHP and PostgreSQL which I presented at O'Reilly OSCON 2002 is now online.



http://www.alcove.com.au/oreilly/

mystran at wasteland dot pp dot htv dot fi
04-Feb-2002 11:46


Nice to know fact that I didn't find documented here.





PHP will return values of PostgreSQL boolean datatype as single character strings "t" and "f", not PHP true and false.





[Editor's Note]


't' or 'f' is valid boolean expression for PostgreSQL.





All values from PostgreSQL are strings, since PostgreSQL integer, float may be much larger than PHP's native int, double can handle. PostgreSQL array is not supported.

saberit at home dot com
15-Sep-2001 05:11


I tried compiling PHP from source with PostgreSQL support (./configure --with-pgsql=/usr/local/pgsql) and ran into a bunch of problems when trying to 'make'. The problem was that some of the PostgreSQL headers were not installed by default when I installed PostgreSQL from source. When installing PostgreSQL make sure you 'make install-all-headers' after you 'make install'.

hubert at hubertmuller dot com
10-Jul-2001 07:36


The best way to find the separated list of tables, sequences, keys etc is:





SELECT relname FROM pg_class WHERE relkind='<value>' AND relname !~ '^pg_';





<value> takes:


i for keys,


r for relations,


S for sequences





Note that all tables names that begins with 'pg_' are PostgreSQL internal tables (this explain why I use AND relname !~ '^pg_' condition).

passion at monkey dot org
28-Jun-2001 09:53


I've tried to mimic the following mysql database connection functions for postgres. 


http://www.php.net/manual/en/function.mysql-list-dbs.php


http://www.php.net/manual/en/function.mysql-list-tables.php





These are assuming that you're passing in $link as the result from pg_connect:





function pg_list_dbs($link)


{  


    $sql = 'SELECT datname FROM pg_database';


    return (pg_query($link, $sql));


}  





function pg_list_tables($link)


{  


    $sql = "SELECT relname FROM pg_class WHERE relname !~ '^pg_'";


    return (pg_query($link, $sql));


}

!spamcraig at ahdore dot com
15-Apr-2001 04:11


If you want to extract data from select statements, you need to store the result index, and then apply pg_result to that value. Basically, do this





$resultIdx = pg_query ($database, "select * from tablename");


$mySelect = pg_fetch_result($resultIdx, 0, 0);  // gets column 0 of tuple 0


echo("My select: [".$mySelect."]");





I'm new to php and had to do some fiddling around to work this out. It's reasonably elementary, but not demonstrated by the examples on these pages. Hopefully it will come in useful to someone else.

bleach at chek dot com
02-Mar-2000 04:36


If you want to see all the objects in a database, you can find that information in the pg_class table. <BR>


SELECT * FROM pg_class;<BR>


Now this is going to be kind of long and complex, to see how psql command handles the \d and other things. use the syntax.  psql -E <Database>, ie psql -E mydatabase <BR>


What this will do is show the SQL command used for everything. So when you type a \d or something, it shows the SQL query used for the result.

add a note