Just a head-up so people don't think we don't care …
I just found a way to reproduce it on one of my Linux boxes. The fail stems from upgrading SQL::Statement from version 1.33 to 1.401 in this combo:
# Using DBI version 1.616
# Using DBD::File version 0.40
# Using SQL::Statement version 1.401
# Using Text::CSV_XS version 0.94
# DBD::CSV 0.36 using Text::CSV_XS (0.94)
# DBD::File 0.40 using IO::File (1.14)
# DBI::DBD::SqlEngine 0.03 using SQL::Statement 1.401
# DBI 1.616
# OS linux (2.6.31.14-0.4-desktop)
# Perl 5.012002 (x86_64-linux-ld)
I started with 5.12.2, as that was one of the reports that CPANTESTERS was kindly showing me and I had available. I am now talking to the author of SQL::Statement to find the cause and a solution :)
Enjoy, Have FUN! H.Merijn
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|