On 15.04.02 at 20:14 Jeff Zucker wrote:
(Sorry Jeff, should have gone to the list)
Thanks, I understand the equijoin now. Unfortunately AnyData is not
happy though. I had to remove all table references or it would complain
that there was no such column as e.g. "NODES.NODETITLE". This is not a
case-sensitivity issue is it? I'm running NT?
Anyhow, I figured if the columns are unique, the table names should not
be required (?). So with this:
SELECT NodeTitle, NodeText, ReferenceType FROM nodes, nodereferences
WHERE RecipientNodeID = NodeID AND NodeID =1
I got these errors:
DBD::AnyData::st execute failed: Can't call method "col_names" o
n unblessed reference at J:/Perl/site/lib/SQL/Statement.pm line
499, <GEN1> line 2.
DBD::AnyData::st execute failed: Can't call method "col_names" o
n unblessed reference at J:/Perl/site/lib/SQL/Statement.pm line
499, <GEN1> line 2.
2) With the second statement it doesn't seem happy even with the table
names omitted and complains that the actual column does not exist. The
columns are defined in the first line of the CSV file, and are there.
The statement:
SELECT NodeTitle, NodeReferenceID
FROM Nodes, NodeReferences
WHERE NodeID = RecipientNodeID
AND ReferringNodeID = '1'
AND ReferenceType = 'child'
Produces this:
Execution ERROR: No such column 'NODEID' called from
D:\wx\anydata_test.pl at 23.
DBD::AnyData::st execute failed: Can't call method "col_names" o
n unblessed reference at J:/Perl/site/lib/SQL/Statement.pm line
499.
DBD::AnyData::st execute failed: Can't call method "col_names" o
n unblessed reference at J:/Perl/site/lib/SQL/Statement.pm line
499.
The CSV has not changed and it just accepted the column names in the
other statement.
Any ideas?
Thanks,
Marcus
