I am looking at an example in the docs for GT::Condition:
'Employer', '=', 'Gossamer Threads'
Shouldn't the '=' be an 'eq', if not why?
I am currently have troubles with this in one of my select statements which fails to return hits even though there is a match:
$cond = GT::SQL::Condition->new( 'Username', 'eq', $USER->{Username}, 'VIN', 'eq', $VIN);
$vt->select( GT::SQL::Condition->new( $cond ) );
if (! $vt->hits ) { etc....
Thanks
EDIT: I just tried the statements with '=' and this seemed to work, and I guess that answers my question. So would I be right in assuming that '=' works for both strings and integers in the SQL::Condition statements and that I should NOT use 'eq'?
http://www.iuni.com/...tware/web/index.html
Links Plugins
'Employer', '=', 'Gossamer Threads'
Shouldn't the '=' be an 'eq', if not why?
I am currently have troubles with this in one of my select statements which fails to return hits even though there is a match:
$cond = GT::SQL::Condition->new( 'Username', 'eq', $USER->{Username}, 'VIN', 'eq', $VIN);
$vt->select( GT::SQL::Condition->new( $cond ) );
if (! $vt->hits ) { etc....
Thanks
EDIT: I just tried the statements with '=' and this seemed to work, and I guess that answers my question. So would I be right in assuming that '=' works for both strings and integers in the SQL::Condition statements and that I should NOT use 'eq'?
http://www.iuni.com/...tware/web/index.html
Links Plugins