LaravelConf Taiwan 2020 CFP Started

dbx 関数


  • dbx_close — オープンされた接続/データベースを閉じる
  • dbx_compare — ソートするために二つのレコードを比較する
  • dbx_connect — 接続/データベースをオープンする
  • dbx_error — 使用するモジュールの最新の関数コールにおけるエラーメッセージを出力する
  • dbx_escape_string — SQL ステートメントで安全に使用できるように文字列をエスケープする
  • dbx_fetch_row — DBX_RESULT_UNBUFFERED フラグを指定した クエリ結果から、行を取得する
  • dbx_query — クエリを送信し、(ある場合には)結果を全て取得する
  • dbx_sort — カスタマイズされたソート関数により、dbx_query から結果をソートする
add a note add a note

User Contributed Notes 5 notes

carl [at] carlthompson [dot] net
16 years ago
The above benchmark is very misleading. Unfortunately, I found out the hard way by porting my app to ADODB. Most PHP apps are going to be very short-lived therefore startup / setup time is a large factor. This benchmark does not measure that. Just include()ing the main ADODB file added 27ms to my app's startup time! Considering my app took only 16ms to run in total using DBX, the idea of switching to ADODB was DOA before running a single query.

In the end, the total time for my app went from 16ms with DBX to 49ms with ADODB. ADODB's powerful features are obviously not worth that kind of overhead.

Carl Thompson
bart at mediawave dot nl
15 years ago
Simple function for returning paged result sets.

// use: pagedQuery($link, $sql, $rows_per_page, $current_page)

function pagedQuery($link, $sql, $nrows = 10, $page = 1) {
$handle = dbx_query($link, $sql, DBX_RESULT_UNBUFFERED);
$result = new stdClass;
$result->link = $this->link;
$result->page = $page;
$result->data = array();
$result->info['name'] = array();
$start = ($page - 1) * $nrows;
$end = $start + $nrows;
$result->rows = 0;
    while (
$row = dbx_fetch_row($handle)) {
        if ((
$result->rows > $start) && ($result->rows <= $end)) {
$result->data[] = $row;           
    if (
$result->data[0]) {
$result->cols = count($result->data[0]) / 2;
$result->info['name'] = array_slice(array_keys($result->data[0]), $result->cols, $result->cols);
$result->lastPage = ceil($result->rows / $nrows);
rhcf at linux dot ime dot usp dot br
16 years ago

dbx_query allocate all retrieved data in an array on memory. If the query result is big (bigger then the memory_limit on php.ini), the result will be empty. So use dbx wih care.
bart at mediawave dot nl
15 years ago
Would like to confirm that dbx is at least three times faster than adodb with my application. However, once loaded, adodb has much more features and probably performs better in some situations then dbx.

One of the nice features that adodb has, is the way you can quickly make a dropdown menu from a query. Here's a similar function that works with a dbx result object:


// $result is the dbx_query result (It expects two fields)
// $name is the name of the dropdown field
// $selected is the option that should be selected
// $firstrow takes a string like "myvalue:myname"
// $attr can be used to add some extra attributes

function dropDown($result, $name, $selected, $firstRow, $attr) {
$s = '<select name="'.$name.'" '.$attr.'>';
    if (
is_string($firstRow))  {
$row = explode(':', $firstRow);
$s .= '<option value="'.$row[0].'">'.$row[1].'</option>';
    } else
$s .= '<option></option>';
    foreach (
$result->data as $row) {
        if (
$row[0] == $selected)
$s .= '<option value="'.$row[0].'" selected="selected">'.htmlspecialchars($row[1]).'</option>';
$s .= '<option value="'.$row[0].'">'.htmlspecialchars($row[1]).'</option>';

jlim at natsoft dot com dot my
17 years ago
For some benchmarks of dbx connecting to mysql compared to native mysql api, adodb, and others, see:
To Top