On Table_1, have a property marked Table_2, mark it lazy load in your result map and when the Table_2 property is called, it will automatically load the records and return the.
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 8:40 AM To: [email protected] Cc: [email protected] Subject: RE: Foreign Key Relationship If I add the relationship to the iBatis config then how do I get the data out of C#? --- [EMAIL PROTECTED] wrote: From: "Clough, Samuel \(USPC.PRG.Atlanta\)" <[EMAIL PROTECTED]> To: <[email protected]> Subject: RE: Foreign Key Relationship Date: Mon, 11 Jun 2007 08:27:19 -0400 I'm a little confused as this seems like something that should be in the resultmap node in the iBatis config if I understand it correctly, not in c# code. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 8:12 AM To: [email protected] Subject: Foreign Key Relationship Is there a way to link 2 table so one of the table_1 C# code can have a getter to get the associated records in table_2. Table_1 ID getTable_2() Table_2 Table1ID (maps to Table_1.ID) getTable_1() So in this case Table_1 would have a getter to get rows from Table_2 and Table_2 have a getter to get rows from Table_1? Also I am using Abator. _____ Princeton Retirement Group, Inc - Important Terms This E-mail is not intended for distribution to, or use by, any person or entity in any location where such distribution or use would be contrary to law or regulation, or which would subject Princeton Retirement Group, Inc. or any affiliate to any registration requirement within such location. This E-mail may contain privileged or confidential information or may otherwise be protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by any mistransmission. Access, copying or re-use of information by non-intended or non-authorized recipients is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail. The transmission and content of this E-mail cannot be guaranteed to be secure or error-free. Therefore, we cannot represent that the information in this E-mail is complete, accurate, uncorrupted, timely or free of viruses, and Princeton Retirement Group, Inc. cannot accept any liability for E-mails that have been altered in the course of delivery. Princeton Retirement Group, Inc. reserves the right to monitor, review and retain all electronic communications, including E-mail, traveling through its networks and systems (subject to and in accordance with local laws). If any of your details are incorrect or if you no longer wish to receive mailings such as this by E-mail please contact the sender by reply E-mail. _____
