EXAMPLE:
You need to know the generator´s value after INSERT:
Before INSERT-Statement run
$nextnumber=ibase_gen_id ("GEN_NAME",1);
GEN_NAME: is the generator´s name
1: means add 1 to actual value of generator
$nextnumber: is variable to store generators value after incrementing
In the INSERT-Statement you can use $nextnumber instead of using generator directly like in:
INSERT INTO test (field1, field2) VALUES gen_id(gen_test_id, 1), 'testme');
ibase_gen_id
(PHP 5)
ibase_gen_id — Incrementa el generador de nombres y devuelve su nuevo valor
Descripción
mixed ibase_gen_id
( string
$generator
[, int $increment = 1
[, resource $link_identifier = NULL
]] )Advertencia
Esta función no está documentada actualmente, solamente se encuentra disponible la lista de parámetros.
Valores devueltos
Devuelve en forma de string el nuevo valor generado, o como string si el valor fuera demasiado grande.
robert ¶
6 years ago
escoric at latinmail dot com ¶
8 years ago
$sql="INSERT INTO mitabla(campo1,campo2,..campo n) VALUES(GEN_ID(mitabla1_codigo_gen,1),'contenido 1', 'contenido 2', 'contenido n' )";
mfischer at php dot net ¶
9 years ago
Question arose on php-dev:
How does ibase_gen_id() handle 64bit values?
Interbase 6/Firebird generators are always 64-bit signed integers
(Firebird's BIGINT type), regardless of the platform the client is
running.
On 64-bit platforms, this will never require conversion as PHP's int
type is 64 bits wide on those platforms. On 32-bit platforms, the
generated value is converted to a string if it exceeds the limits of a
32-bit signed integer.
(This behaviour is consistent with the ibase_fetch_*() functions, that
will use strings to represent numerical values that cannot be represented
accurately using native PHP numerical types.)
[Edited by PHP/Interbase maintainer.]
