TOracleQuery.Optimize Versions

[T Steenson]

When upgrading from an old 3.4 version to 4.0.x there is the following compatibility issue in the readme file.

- TOracleQuery.Optimize now implicitly closes queries when done

Can you tell me a little more about this change? What does "done" mean in this case and what are the performance implications with the old and new behavior?

Thanks.

 

[Marco Kalter]

If Optimize = False, and the query is done (for a select statement this means all rows are retrieved), then it is implicitly closed. There are no performance consequences, but you may see fewer open cursors on the server.