The row $whole_file = ; student bee there, its an cut and paste
error. It's not in the original code.
I did a run now and it takes 237 seconds.
/Ulf
At 13:13 2003-08-20, Carl Jolley wrote:
On Wed, 20 Aug 2003, Ulf Lowig wrote:
> Hi, thanks fore the answers from all of you.
>
> One question th
On Wed, 20 Aug 2003, Ulf Lowig wrote:
> Hi, thanks fore the answers from all of you.
>
> One question that frequent comes back to me is why I am reading it to a
> memory. The answer is, I am not going to read it into memory, I plan to
> open a file handle and insert the hole file into as MS SQL se
Hi, thanks fore the answers from all of you.
One question that frequent comes back to me is why I am reading it to a
memory. The answer is, I am not going to read it into memory, I plan to
open a file handle and insert the hole file into as MS SQL server 2000.
When I run insert to SQL server th
On Wed, 20 Aug 2003 [EMAIL PROTECTED] wrote:
> > freed and available segment of memory that was used. My WAG is that if
> > you changed the order of the different ways of reading the whole file,
> > the first read will take longer than the others.
>
> Exactly.
> Anyway the time is the order of a f
