Subject | TIB_Query buffering |
---|---|
Author | georgethenorge |
Post date | 2002-04-21T05:35:57Z |
One of my performance increasing tricks has been to take a query and put the contents in an array. Then, I do all of my operations on the array, and put it back in the query when I am done. This works well for a GUI where the user is jockeying 100 different elements around the screen.
What I am wondering is - what are the performance differences between this and just using a TIB_Query as is, with locates, etc?
I would assume that writing would be slower, because of the overhead involved in actually posting the changes to the server.
What about reading? How does that compare?
If you know the index of an array, you can get to that particular element in no time. Is there some way to use the buffer in TIB_Query in a similar fashion with the KeyLinks parameter?
Thanks
George Helmke
What I am wondering is - what are the performance differences between this and just using a TIB_Query as is, with locates, etc?
I would assume that writing would be slower, because of the overhead involved in actually posting the changes to the server.
What about reading? How does that compare?
If you know the index of an array, you can get to that particular element in no time. Is there some way to use the buffer in TIB_Query in a similar fashion with the KeyLinks parameter?
Thanks
George Helmke