|Subject||RE: [firebird-support] Re: generator ids in uncommitted transactions|
> I am using this to keep track of changes so that they can be cachedsince generators are fired outside transaction control there is no
> for example in an application. To do this, it's easy to select all the
> rows that have the id greater than the id I saw last time.
> Therefore I need to know if any transaction with a lower id might now
> commit in the future.
relationship here (necessarily)...
Tell us what component set you are using and a little more about what this
caching is all about and someone may have some suggestions for you.
you talk about a lower id commiting but also about selecting higher ids so I
can't quite follow.
But there is already some very good caching going on in some component
tell us more about the size of the datasets you are experiencing, whether
local or remote connections etc
> --- In email@example.com, "Alan McDonald" <alan@m...>
> > >
> > > Is there any way to find out if there are any uncommitted
> > > that have called gen_id on a generator ?
> > > Or if I get an id using the gen_id call, can I somehow wait till
> > > current transactions either commit or abort ?
> > >
> > > Thanks!
> > >
> > uh oh... what are you trying to do... sounds fishy
> > Alan