Jeff Zucker [EMAIL PROTECTED] wrote in message
news:3DB98694.8080701;vpservices.com...
Yes, there is a bug in SQL::Statement related to table names combined with
a column name (e.g. megaliths.id).
I will be releasing a fix later today.
Thank you oh great and wise one! I appreciate the help and
It appears from the error message that it cannot locate the CSV file
at all. Are you sure:
$dbd = DBI:CSV:f_dir=magalith_db;
Is correct? You've spelled 'megalith' as 'magalith'. Just have to
check. I assume you've got whatever dir on the same level as your
script and that you've got a file
[EMAIL PROTECTED] wrote in message
news:1842904766.20021025094128;comcast.net...
It appears from the error message that it cannot locate the CSV file
at all. Are you sure:
$dbd = DBI:CSV:f_dir=magalith_db;
Is correct? You've spelled 'megalith' as 'magalith'. Just have to
check. I assume
Scott McGee wrote:
SQL::Parser v1.004
SQL::Statement v1.004
...
my $query = SELECT megaliths.id, megaliths.name, site_types.site_type
Yes, there is a bug in SQL::Statement related to table names combined with a column name (e.g. megaliths.id).
I will be releasing a fix later today.
On Friday, October 25, 2002 11:01 PM [GMT + 10:00 AEST],
Scott McGee [EMAIL PROTECTED] wrote:
I am trying to get comfortable with DBI, and due to stupid
circumstances beyond my control at the moment, have to try to make do
without an actual database server. This means using something like
