This project aims to repackage the old ibase extension into a more modern PHP framework. Internal resource types have been removed and replaced with a object-oriented interface. Most of the ibase extension features have now been ported; however, development is still in progress, and the API is not yet stable.
Current development environment: PHP 8.4.4 NTS, Firebird 5.0.2, Debian 12 (64-bit).
Currently supported PHP version: 8.4.x
<?php declare(strict_types = 1);
$args = new \FireBird\Connect_Args;
$args->database = "localhost:/opt/db/test.fdb";
$args->user_name = "sysdba";
$args->password = "masterkey";
$db = \FireBird\Database::connect($args);
$t = $db->start_transaction();
$q = $t->query("SELECT * FROM TEST_TABLE");
while ($r = $q->fetch_object(\FireBird\FETCH_FETCH_BLOB_TEXT)) {
print_r($r);
}Some example code can be fetched from tests
PHP stub file: firebird.stub.php
phpize
./configure --with-firebird
make
make install
Optionally specify Firebird 5.0 path: --with-firebird=/opt/firebird
- Install PHP SDK: https://github.com/microsoft/php-sdk-binary-tools
- Install git, add to PATH
- Copy build scripts from win32 to C:\php-sdk\
- Adjust php-firebird-config.bat. PFB_SOURCE_DIR should point one level up, e.g. if you clone firebird-php into D:\firebird-php\firebird-php, then PFB_SOURCE_DIR=D:\firebird-php\
cd C:\php-sdk\
php-firebird-build-all.bat
| Function | Notes | |
|---|---|---|
| ❌ | ibase_add_user | C++ refactoring needed |
| ✅ | ibase_affected_rows | |
| ❌ | ibase_backup | C++ refactoring needed |
| ✅ | ibase_blob_add | |
| ✅ | ibase_blob_cancel | |
| ✅ | ibase_blob_close | |
| ✅ | ibase_blob_create | |
| 🚫 | ibase_blob_echo | Can be easily done from PHP |
| ✅ | ibase_blob_get | |
| 🚫 | ibase_blob_import | Can be easily done from PHP |
| ✅ | ibase_blob_info | |
| ✅ | ibase_blob_open | |
| ✅ | ibase_close | |
| ✅ | ibase_commit | |
| ✅ | ibase_commit_ret | |
| ✅ | ibase_connect | |
| 🚫 | ibase_db_info | Not worth it. It appears this returns unstructured data anyways. |
| ❌ | ibase_delete_user | C++ refactoring needed |
| ✅ | ibase_drop_db | |
| ✅ | ibase_errcode | Via exceptions |
| ✅ | ibase_errmsg | Via exceptions |
| ✅ | ibase_execute | |
| ✅ | ibase_fetch_assoc | |
| ✅ | ibase_fetch_object | |
| ✅ | ibase_fetch_row | |
| ✅ | ibase_field_info | |
| ❌ | ibase_free_event_handler | C++ refactoring needed |
| ✅ | ibase_free_query | |
| ✅ | ibase_free_result | |
| 🚫 | ibase_gen_id | Can be easily done from PHP |
| ❌ | ibase_maintain_db | C++ refactoring needed |
| ❌ | ibase_modify_user | C++ refactoring needed |
| ❌ | ibase_name_result | C++ refactoring needed |
| ✅ | ibase_num_fields | |
| ✅ | ibase_num_params | |
| ✅ | ibase_param_info | |
| ❓ | ibase_pconnect | Not sure if this is a good idea. Most likely this will be used inproperly anyways, leaving around long running transactions. ALTER SESSION RESET |
| ✅ | ibase_prepare | |
| ✅ | ibase_query | |
| ❌ | ibase_restore | C++ refactoring needed |
| ✅ | ibase_rollback | |
| ✅ | ibase_rollback_ret | |
| ❌ | ibase_server_info | C++ refactoring needed |
| ❌ | ibase_service_attach | C++ refactoring needed |
| ❌ | ibase_service_detach | C++ refactoring needed |
| ❌ | ibase_set_event_handler | |
| ✅ | ibase_trans | |
| ❌ | ibase_wait_event |
- Collect opened and not closed statements/transactions/blobs/etc and report
- Test on Windows and different PHP versions.
- isc_info_sql_get_plan, isc_info_sql_explain_plan and other information
IStatement::createBatch, IAttachment::createBatch
- When inserting/updating large amounts of data.
- When reducing network round trips is critical.
- When handling bulk inserts with RETURNING values.
- When performing batch deletes/updates efficiently.
Is it worth even supporting array type? Firebird docs thinks not: https://firebirdsql.org/file/documentation/html/en/refdocs/fblangref50/firebird-50-language-reference.html#fblangref50-datatypes-array
Firebird does not offer much in the way of language or tools for working with the contents of arrays, and there are no plans to improve this. This limits the usefulness and accessibility of array types. Therefore, the general advice is: do not use arrays.
Arrays introduce unnecessary complexity. You can't even INSERT / UPDATE array fields using DSQL, just with isc API or PSQL. If arrays are needed these can be implemented using relation model.
