If you are using VirtualHosts with Apache, you might find useful the following directive:
php_flag magic_quotes_sybase on
Use it in any VirtualHost and it will be set locally to that VirtualHost without interfering with any global setting.
This is an example:
<VirtualHost 555.666.777.888>
ServerName www.samplehost.com
DirectoryIndex index.php index.htm
php_flag magic_quotes_sybase on
</VirtualHost>
Firebird/InterBase Funzioni
Indice dei contenuti
- fbird_add_user — Alias di ibase_add_user
- fbird_affected_rows — Alias di ibase_affected_rows
- fbird_backup — Alias di ibase_backup
- fbird_blob_add — Alias di ibase_blob_add
- fbird_blob_cancel — Cancel creating blob
- fbird_blob_close — Alias di ibase_blob_close
- fbird_blob_create — Alias di ibase_blob_create
- fbird_blob_echo — Alias di ibase_blob_echo
- fbird_blob_get — Alias di ibase_blob_get
- fbird_blob_import — Alias di ibase_blob_import
- fbird_blob_info — Alias di ibase_blob_info
- fbird_blob_open — Alias di ibase_blob_open
- fbird_close — Alias di ibase_close
- fbird_commit_ret — Alias di ibase_commit_ret
- fbird_commit — Alias di ibase_commit
- fbird_connect — Alias di ibase_connect
- fbird_db_info — Alias di ibase_db_info
- fbird_delete_user — Alias di ibase_delete_user
- fbird_drop_db — Alias di ibase_drop_db
- fbird_errcode — Alias di ibase_errcode
- fbird_errmsg — Alias di ibase_errmsg
- fbird_execute — Alias di ibase_execute
- fbird_fetch_assoc — Alias di ibase_fetch_assoc
- fbird_fetch_object — Alias di ibase_fetch_object
- fbird_fetch_row — Alias di ibase_fetch_row
- fbird_field_info — Alias di ibase_field_info
- fbird_free_event_handler — Alias di ibase_free_event_handler
- fbird_free_query — Alias di ibase_free_query
- fbird_free_result — Alias di ibase_free_result
- fbird_gen_id — Alias di ibase_gen_id
- fbird_maintain_db — Alias di ibase_maintain_db
- fbird_modify_user — Alias di ibase_modify_user
- fbird_name_result — Alias di ibase_name_result
- fbird_num_fields — Alias di ibase_num_fields
- fbird_num_params — Alias di ibase_num_params
- fbird_param_info — Alias di ibase_param_info
- fbird_pconnect — Alias di ibase_pconnect
- fbird_prepare — Alias di ibase_prepare
- fbird_query — Alias di ibase_query
- fbird_restore — Alias di ibase_restore
- fbird_rollback_ret — Alias di ibase_rollback_ret
- fbird_rollback — Alias di ibase_rollback
- fbird_server_info — Alias di ibase_server_info
- fbird_service_attach — Alias di ibase_service_attach
- fbird_service_detach — Alias di ibase_service_detach
- fbird_set_event_handler — Alias di ibase_set_event_handler
- fbird_trans — Alias di ibase_trans
- fbird_wait_event — Alias di ibase_wait_event
- ibase_add_user — Add a user to a security database
- ibase_affected_rows — Return the number of rows that were affected by the previous query
- ibase_backup — Initiates a backup task in the service manager and returns immediately
- ibase_blob_add — Add data into a newly created blob
- ibase_blob_cancel — Cancel creating blob
- ibase_blob_close — Close blob
- ibase_blob_create — Create a new blob for adding data
- ibase_blob_echo — Output blob contents to browser
- ibase_blob_get — Get len bytes data from open blob
- ibase_blob_import — Create blob, copy file in it, and close it
- ibase_blob_info — Return blob length and other useful info
- ibase_blob_open — Open blob for retrieving data parts
- ibase_close — Close a connection to an InterBase database
- ibase_commit_ret — Commit a transaction without closing it
- ibase_commit — Commit a transaction
- ibase_connect — Open a connection to a database
- ibase_db_info — Request statistics about a database
- ibase_delete_user — Delete a user from a security database
- ibase_drop_db — Drops a database
- ibase_errcode — Return an error code
- ibase_errmsg — Return error messages
- ibase_execute — Execute a previously prepared query
- ibase_fetch_assoc — Fetch a result row from a query as an associative array
- ibase_fetch_object — Get an object from a InterBase database
- ibase_fetch_row — Fetch a row from an InterBase database
- ibase_field_info — Get information about a field
- ibase_free_event_handler — Cancels a registered event handler
- ibase_free_query — Free memory allocated by a prepared query
- ibase_free_result — Free a result set
- ibase_gen_id — Increments the named generator and returns its new value
- ibase_maintain_db — Execute a maintenance command on the database server
- ibase_modify_user — Modify a user to a security database
- ibase_name_result — Assigns a name to a result set
- ibase_num_fields — Get the number of fields in a result set
- ibase_num_params — Return the number of parameters in a prepared query
- ibase_param_info — Return information about a parameter in a prepared query
- ibase_pconnect — Open a persistent connection to an InterBase database
- ibase_prepare — Prepare a query for later binding of parameter placeholders and execution
- ibase_query — Execute a query on an InterBase database
- ibase_restore — Initiates a restore task in the service manager and returns immediately
- ibase_rollback_ret — Roll back a transaction without closing it
- ibase_rollback — Roll back a transaction
- ibase_server_info — Request information about a database server
- ibase_service_attach — Connect to the service manager
- ibase_service_detach — Disconnect from the service manager
- ibase_set_event_handler — Register a callback function to be called when events are posted
- ibase_trans — Begin a transaction
- ibase_wait_event — Wait for an event to be posted by the database
add a note
User Contributed Notes 6 notes
interbase at almico dot com ¶
22 years ago
lars at dybdahl dot net ¶
22 years ago
It is not possible to use interbase/firebird without initiating transactions. It seems that transactions are not automatically committed or rolled back at the end of a script, so remember to end all interbase enabled scripts with ibase_rollback() or ibase_commit().
Worse is, that if you use ibase_pconnect (recommended), transactions survive from one request to the next. So that if you don't rollback your transaction at the end of the script, another user's request might continue the transaction that the first request opened.
This has two implications:
1) Clicking refresh in your browser won't make you see newer data, because you still watch data from the same transaction.
2) Some php scripts might fail occassionally and not fail in other occasions, depending on with apache server thread and thereby which transaction they start using.
Unfortunately, there is no such thing as
if (ibase_intransaction()) ibase_rollback();
so be sure that ALL your scripts end with an ibase_rollback() or ibase_commit();
felixlee at singnet dot com dot sg ¶
21 years ago
Here's an example for getting results back from stored procedure in firebird.
The example make use of the stored procedure in Employee.gdb and the show_langs procedure.
$host = 'localhost:X:/firebird/examples/Employee.gdb';
$username='SYSDBA';
$password='masterkey';
$dbh = ibase_connect ( $host, $username, $password ) or die ("error in db connect");
$stmt="Select * from SHOW_LANGS('SRep',4,'Italy')";
$query = ibase_prepare($stmt);
$rs=ibase_execute($query);
$row = ibase_fetch_row($rs);
echo $row[0];
/* free result */
ibase_free_query($query);
ibase_free_result($rs);
/* close db */
ibase_close($dbh);
?>
sysop at smartnettechnologies dot com ¶
17 years ago
This example have 2 problems my be the autor writes it to fast but in the first case use one var for define user pass and and the use other one for call them and in secon step use comas after the ;
$db = '/path/to/database.gdb';
$user = 'username';
$password = 'password';
$res = ibase_connect($db,$dbuser,$dbpass) or die("<br>" . ibase_errmsg());
// Query
$sql="SELECT * FROM table;"
johan at essay dot org ¶
24 years ago
For those who have problem with returning values from Stored Procedures in PHP-Interbase, I have found a solution. Use a select sentence like this:
select * from sp_prodecure(param, ...)
However, it is important that the procedure has a SUSPEND statement or else the procedure won't return any values.
But the "message length" (see above note) bug that you encounter when you try to execute a procedure should be fixed !
fortega at uamericas dot net ¶
17 years ago
Here is a minimalistic code example. Be sure to create an user and a database in order to make it work.
<?php
// Minimalistic code example
// Connection
$db = '/path/to/database.gdb';
$user = 'username';
$password = 'password';
$res = ibase_connect($db,$dbuser,$dbpass) or die("<br>" . ibase_errmsg());
// Query
$sql="SELECT * FROM table;"
$result=ibase_query($res,$sql) or die(ibase_errmsg());
while($row=ibase_fetch_object($result)){
// use $row->FIELDNAME not $row->fieldname
print $row->FIELDNAME;
}
ibase_free_result($result);
// Closing
ibase_close($res) or die("<br>" . ibase_errmsg());
?>
The following code can be used when creating tables in order to get auto incrementing fields:
<?php
// This function generates an autoincrement field, such as MySQL AUTO_INCREMENT.
function generate_autoincrement($tablename,$primarykey){
// * Generator
dbexec('CREATE GENERATOR GEN_' . $tablename . '_PK;');
// * Trigger
dbexec('CREATE TRIGGER INC_' . $primarykey . ' FOR ' . $tablename
. chr(13) . 'ACTIVE BEFORE INSERT POSITION 0'
. chr(13) . 'AS'
. chr(13) . 'BEGIN'
. chr(13) . 'IF (NEW.' . $primarykey . ' IS NULL) THEN'
. chr(13) . 'NEW.' . $primarykey . '= GEN_ID(GEN_' . $tablename . '_PK, 1);'
. chr(13) . 'END');
}
?>
Usage: <?php generate_autoincrement('table','column name'); ?>
