Search results for query: *

All, I have modified the script with WIN32::Process command to launch the parsing script. The logic goes 'wait for the parser to finish for 60 seconds, if it does not finish kill it'. This is safe enough as the the parser never runs more than a few seconds when operating right (not...

...meanwhile...back at the ranch... I found the error causing the 'too long for column error...fixed it. Pfist, the date thing worked...fixed it The script runs blazing fast now...right up to when it sticks. The sticks are either at an execute statement, commit statement, or when calling a...

Well, here goes... I have narrowed the 'sticking' point to two places. 1. the 'prepare' statement, 2. the 'commit' statement...the prepare is usually the sticking point. Here is the flow of the script: I have a small script which runs in a while loop that recursively calls the...

Ok, I tried splitting up the script (which works nicely) but unfortunately the 'sticking' still occurs. I have determined the problem is not memory since the size of perl.exe never seems excessive (it loads at 10MB) and may or may not grow before sticking. I have placed a bunch of little...

Actually, yes. I sat and watched just exactly that the other day (a lot like watching paint dry) and saw that it grew in (apparently) 4KB chunks. I realize the chunk size might be as much a "Task Manager" ism as anything. Anyway, I noticed the size only grew when some errors went...

I will certainly try that. Question...do errors eat up memory? Like if I get a "uninitialized string" error, do these errors use memory then not release it? I ask this because I had had several of these which I subsequently cleared up and the run time increased. I still get one of...

I have a script runs a while() loop and sleeps for 4 seconds between iterations. This script reads files from a directory that is continuously fed small text files, which the script reads in, parses out (the data is weather observations), then databases in an Oracle 8i database...