mlazdans

Requires optional argument

1

**Describe the bug** Intelephense requires an optional argument. **To Reproduce** ```

Some tests reporting memory leaks with PHP 8.4 debug mode

1

Did not test on other PHP versions yet but on PHP 8.4 (Zend Extension Build => API420240924,NTS,debug) these tests fail with memory leaks or assersions: 1. InterBase: connect, close and...

Confusing PHP documentation for ibase_trans()

2

Reading the PHP documentation, it appears that the order in which we pass _link_identifier_ and _trans_args_ arguments to **ibase_trans()** does not matter.  However, this is not quite true. If...

tests/008.php fail with PHP 8.4: Maximum call stack size reached

2

``` tests/008.php Fatal error: Uncaught Error: Maximum call stack size of 8355840 bytes (zend.max_allowed_stack_size - zend.reserved_stack_size) reached. Infinite recursion? in tests/008.php:9 Stack trace: #0 [internal function]: event_callback('TEST2', Resource id #12)...

Ibase result

2

Sorry for large (again) pull request, it just happened 😬 Please test it thoroughly first. Address issues: - #75 - #79 - #80 - #81 - #84 - #87 -...

ibase_fetch with IBASE_UNIXTIME flag returns negatives from TIME fields

1

Does it even make sense converting TIME fields into Unix timestamp? 🤔 ```php ibase_query("CREATE TABLE TTEST ( ID INTEGER, T1 TIME DEFAULT '15:45:59', T2 TIMESTAMP DEFAULT '2025-11-06 15:45:59' )"); ibase_commit();...

Related to #82 We have defined resource names ```c #define LE_LINK "Firebird/InterBase link" #define LE_PLINK "Firebird/InterBase persistent link" #define LE_TRANS "Firebird/InterBase transaction" ``` Then we have defined query associated resources...

Not a single test covering `ibase_name_result()`

From PHP manual: 1. Arguments for `ibase_query()` is not documented properly. They should be like this: ```php ibase_query(string $query [, mixed ...$bind_args]): resource ibase_query(resource $link_identifier, string $query [, mixed ...$bind_args]):...