Subject | Re: [IBO] Transactions - snapshot of data |
---|---|
Author | Robert martin |
Post date | 2006-05-03T05:03Z |
Hi
Not really :) we are looking at a maximum of 24 records to return and
with just locating in the buffers it shouldn't be a big deal. It is a
nice way to solve a problem that is simple and straight forward.
Not to worried about the 'just 1 calorie' version as this is a very
small and infrequently used operation, I just got worried when it wasn't
working as expected :)
Rob Martin
Software Engineer
phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com
Wild Software Ltd
Helen Borrie wrote:
Not really :) we are looking at a maximum of 24 records to return and
with just locating in the buffers it shouldn't be a big deal. It is a
nice way to solve a problem that is simple and straight forward.
Not to worried about the 'just 1 calorie' version as this is a very
small and infrequently used operation, I just got worried when it wasn't
working as expected :)
Rob Martin
Software Engineer
phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com
Wild Software Ltd
Helen Borrie wrote:
>At 12:25 PM 3/05/2006, you wrote:
>
>
>This approach has all the hallmarks of using a sledgehammer to crack
>a nut. You wrote: "The theory is that if I do a locate in the Query
>and don't find the record I know it is an addition." What's the
>purpose of this? If your read-write transaction posts and commits an
>insert, you'll already know it is an addition...Locate() is a very
>heavy way of confirming what you already know. Just create a flag
>that you can set and reset - low-calorie and no cost.
>
>Helen
>
>
>