Trouble with relationship errors
Archived from the Xataface Users forum.
clester — Wed Dec 06, 2006 7:32 am
Hi,
I have been having trouble with dataface. I have a few simple tables with one to many relationships. The tree works ok but the tabs give me this:
Catchable fatal error: Object of class Dataface_SkinTool could not be converted to string in C:\wamp\www\dataface\Dataface\Error.php on line 64
DF Version : 0.6.9r1
tables are as follows:
CREATE TABLE cards (
card\_id int(11) NOT NULL auto_increment,
card\_name varchar(150) NOT NULL,
primary\_borrower varchar(100) NOT NULL,
secondary\_borrower varchar(100) default NULL,
phone varchar(10) default NULL,
mobile varchar(10) default NULL,
fax varchar(10) default NULL,
email varchar(50) default NULL,
address varchar(150) NOT NULL,
suburb varchar(50) NOT NULL,
post\_code char(4) NOT NULL,
PRIMARY KEY (card\_id),
KEY card\_name (card\_name)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=7 ;
CREATE TABLE loans (
loan\_id int(11) NOT NULL auto_increment,
card\_id int(11) NOT NULL,
lender int(11) NOT NULL,
loan\_amount decimal(10,0) default NULL,
property\_value decimal(10,0) NOT NULL,
secuity text NOT NULL,
lender\_ref varchar(20) NOT NULL default ‘Unknown’,
status int(11) NOT NULL default ‘0’,
start\_date timestamp NOT NULL default CURRENT_TIMESTAMP,
processor int(11) NOT NULL,
PRIMARY KEY (loan\_id),
UNIQUE KEY lender\_ref (lender\_ref),
KEY card\_id (card\_id)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;
the relationship.ini in the cards dir:
[Loans]
loans.card_id = “$card_id”
Any help would be greatly appreciated
Regards
shannah — Wed Dec 06, 2006 12:07 pm
This error appears to be happening in the error handler - so there may be another error that is causing this one that we don’t get to see. I have added an issue and uploaded a new version of Dataface_Error that should correct this issue - and allow us to see what the real error is.
http://framework.weblite.ca/development/issue-tracker/139
-Steve
clester — Wed Dec 06, 2006 4:51 pm
Hi Steve,
Thanks for your help. The patch has fixed the problem. There was no other error.
Perhaps its a windows-centric thing. I am using the latest wampserver stack for development.
A great product and great support.
Thanks again.