Riverside-Software
Rule: Default Buffer Usage
Is it possible to get a "light" rule for this. As far as I know, using default buffers with no-lock doesn't have the mentioned problems and can be intended.
Suggestion: Forbid default buffer usage for CREATE, DELETE and queries with EXCLUSIVE-LOCK.
There are still problems that can happen even with no lock. Just because i am curious, what is the reasoning behind using global buffers? I don't see a single advantage
Hello movedoa,
Let's say, you have a join with 5 database tables and you want to generate a report or copy/add/multiply a lot of the fields of these 5 database tables into a temptable. I usually open the query and then calling different private method for this task.
Binding Datasets between different source files (UI +ClientBusinessLogikClasses) is another case for the default buffer. If you use the default temptable buffer for the query in a browse, the selected record is available in your ClientBusinessLogikClass - that is very handy.
Another case for binded/reference-only Datasets: You can not define a buffer as parameter for reference-only temptables.
Kind regards, Lars Neumeier