Hello,

I've been debugging a multithreaded database app. In my app I generate lots
of queries. It has crashed or been reset a lot. Now I've noticed that there
are hundreds of .dat, .blb and .idx files that got left behind when the app
disappeared.

Whats the logic behind this? When do queries get streamed to disk, and are
there any builtin cleanup routines?

cheers

Marc Pelletier
Goldak Airborne Surveys

Hi Marc,

Temporary table are created for Alter, Optimize and UpgradeTable operations
and for canned queries. You can configure where the temporary tables are
create by setting the TDBISAMSession PrivateDir property. Temporary tables
are cleaned up when an application closes normally, I don't think it
unreasonable to expect "left-overs" if this does not happen.

HTH
--
Best regards

Steve
"Marc Pelletier" <marc@stopspam.goldak.ca> wrote in message
news:Xns97EAAD68F47D5mmpp1234.dd@64.65.248.118...
> Hello,
>
> I've been debugging a multithreaded database app. In my app I generate
> lots
> of queries. It has crashed or been reset a lot. Now I've noticed that
> there
> are hundreds of .dat, .blb and .idx files that got left behind when the
> app
> disappeared.
>
> Whats the logic behind this? When do queries get streamed to disk, and are
> there any builtin cleanup routines?
>
> cheers
>
> Marc Pelletier
> Goldak Airborne Surveys

Steve Forbes wrote:
> Hi Marc,
>
> Temporary table are created for Alter, Optimize and UpgradeTable
> operations and for canned queries. You can configure where the
> temporary tables are create by setting the TDBISAMSession PrivateDir
> property. Temporary tables are cleaned up when an application closes
> normally, I don't think it unreasonable to expect "left-overs" if
> this does not happen.

More exactly: they are cleand up right after they are not needed anymore. If
you close a query that is represented by a temporarily created table, the
table is deleted. Same with ALTER TABLE. After that operation is done, the
temp files will be deleted. Not the backup files, of course, if you don't
add NOBACK to the SQL statement.

Ralf

Marc,

These free (with full source) components make threading an absolute, safe as houses,
pleasure.  If you use threads, take the 15 minutes out of your day to try them out.

The design time editors are magic and make your threading code trivial to maintain as well.

http://www.mitov.com/BMDelphiThread.zip

Hey, you mentioned threads

Cheers,
Graham W.

Graham Wood <gdwfleetware@netscape.net> wrote in
news:BA745BEE-2E33-4B67-9E7F-2459D2ECB422@news.elevatesoft.com:

> These free (with full source) components make threading an absolute,
> safe as houses, pleasure.  If you use threads, take the 15 minutes out
> of your day to try them out.
>

Thanks Graham, I will take a look, but there doesn't seem to be any
documentation.

I've put it on my take-a-look list.

cheers

Marc

"Graham Wood" <gdwfleetware@netscape.net> wrote in message
news:BA745BEE-2E33-4B67-9E7F-2459D2ECB422@news.elevatesoft.com...
> These free (with full source) components make threading an absolute, safe
> as houses,
> pleasure.  If you use threads, take the 15 minutes out of your day to try
> them out.
>
> The design time editors are magic and make your threading code trivial to
> maintain as well.
>
> http://www.mitov.com/BMDelphiThread.zip

Is there any documentation or examples for these components out there? I
downloaded them and would like to give them a try. I did a google and a
tamarack search, but found nothing.

Thanks,
Johnnie