Is this a risk with SELECT for input only?

I am on a 170 with slowly eroding disk space (just hit 80%) and constant drumbeat of various other demands on my time such that I rarely able to work on disk space topic.

I use SQL very heavily to GET data via individual SELECT or via CURSOR loop.
I am not using it for actual updates.

> When SQL is used, database
> modifications stay in "temporary storage" until a commit is performed.
> If commits are not done by the client-side application in a timely
> manner a system can shut down due to lack of disk space.

There's an interesting attack vector. Perform an update over and over
and over w/out committing it and you'll crash your machine. :)

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.