Subject | Re: [Firebird-Architect] Generator security - from Database trigger thread |
---|---|
Author | Geoff Worboys |
Post date | 2006-09-20T00:58:40Z |
I wrote:
store the increment as part of the generator definition".
If the increment was part of the generator definition then
the "standard" would be defined. That aspect is not feasible
with the current implementation.
Where are you with the new SQL standard syntax "NEXT VALUE"?
It seems you are stuck with using non-standard gen_id. Whereas
if the increment was part of the generator definition you could
use the NEXT VALUE syntax.
--
Geoff Worboys
Telesis Computing
>> Being able to differentiate between a standard increment andAlan wrote:
>> non-standard increment (except that we dont seem to store the
>> increment as part of the generator definition) could be a mid-
>> way step. You could then allow read or read/write access to
>> the generator. Read access would allow "next value"
>> (gen_id(xxx, 1)) but only write access could alter sequence.
> And what exactly is a non-standard increment? I haveThat was the point of my comment "except that we dont seem to
> replication servers and 10 as the basic increment
store the increment as part of the generator definition".
If the increment was part of the generator definition then
the "standard" would be defined. That aspect is not feasible
with the current implementation.
Where are you with the new SQL standard syntax "NEXT VALUE"?
It seems you are stuck with using non-standard gen_id. Whereas
if the increment was part of the generator definition you could
use the NEXT VALUE syntax.
--
Geoff Worboys
Telesis Computing