Hello Jeff,

I believe the problem of the low speed is due using SQL-Statement 1.005. I
think I should change to a XS Version  like 0.1021.

But from where can I get such a package? I have loaded it initaly from
ActivePerl. But the package they provide there for 6xx build (5.6.1) has
only the SQL-Statement 1.005. The 5xx buid is using SQL-Statement 0.1021,
but I can not install this package on my system.

Any info where I can get this package would be of great help.

Peter

----- Original Message -----
From: "Jeff Zucker" <[EMAIL PROTECTED]>
To: "Peter Schuberth" <[EMAIL PROTECTED]>; "dbi-users" <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 7:07 PM
Subject: Re: DBD::CSV


> Peter Schuberth wrote:
>
> >On the same hardware system
> >the same select for the same table
> >
> Please check your version of SQL::Statement which is the module that
> determines the speed and capabilities of DBD::CSV.  Put these two lines
> at the top of the scripts:
>
>     use SQL::Statement;
>     print $SQL::Statement::VERSION;
>
> It sounds to me like you may have the XS version of the module on one
> install and the pure perl version on the other.  You can read about the
> difference between the two at
>
>    http://www.vpservices.com/jeff/programs/sql-compare.html
>
> If you have a moderately large data set and speed is an issue, then the
> XS version will be better but MySQl, PostgreSQL, or SQLlite will be even
> faster. DBD::CSV is really meant for relatively small data sets and
> relatively uncomplicated querries.
>
> Another issue:  if you are trying to access the same data file from both
> windows and linux, you'll need to specifically set the csv_eol for the
> table.  It doesn't really  matter which you choose, either "\015\012" or
> "\012".  If the script sets it to either one of those and the data
> matches, then the same file can be accessed from both windows and linux
> without changing the file or the script.  That sort of multi-platform
> accessibility can be achieved with the other DBDs, but probably not as
> simply.
>
> You may be running into some bugs I am working on relatvie to
> parentheses in WHERE clauses.  I'd appreciate it if you could send me
> any sample queries that don't work for you.
>
> --
> Jeff
>
>

Reply via email to