Subject | Re: [firebird-support] firebird deadlock vs isc_tpb_wait/etc. issue, or ? |
---|---|
Author | Ann W. Harrison |
Post date | 2006-10-18T15:31:12Z |
learntrade wrote:
made somewhat harder (in my opinion) by the matrix of transaction
modes and options. The easy answer is to use the facility provided,
i.e. generators. If you're worried about portability, the SQL standard
committee has endorsed "sequences" which are much like generators and
Firebird 2 implements the standard syntax.
Even if you get your procedure to work, it will be MUCH slower than
generators.
Regards,
Ann
>Err, that's exactly why generators were created. It's a hard problem,
> I am basically trying to update a value (similar to a generator), and
> return that "next" value to serve multiple requesting clients (only
> one value to one client at a time).
made somewhat harder (in my opinion) by the matrix of transaction
modes and options. The easy answer is to use the facility provided,
i.e. generators. If you're worried about portability, the SQL standard
committee has endorsed "sequences" which are much like generators and
Firebird 2 implements the standard syntax.
Even if you get your procedure to work, it will be MUCH slower than
generators.
Regards,
Ann