Hi Jaromir, That example is based on GUID OIDs. You can change the table structure to Integer if you're using Integer OIDs.
Personally, I don't use Foreign Keys or any other kind of Referential Integrity in the database. I handle it all in my application/object model with all the other business rules. I treat the database as somewhere just to keep my stuff and that's all. Everything else I implement in the object layer. Regards, Andy -----Original Message----- From: Jaromir [mailto:[email protected]] Sent: Thursday, July 15, 2010 2:57 PM To: [email protected] Subject: Re: [tiOPF-talk] Demo_11_OnetoMany question W dniu 2010-07-15 10:57, Andrew Denton pisze: > Hi Jaromir, > > Rather than embed OIDs in the database, I use the Relationship Manager > pattern - it's much more flexible and makes your code easier to maintain. > There's an example in the Quarantine directory. All that Owner.Owner.OID > stuff is just wrong, IMHO. Thanks, I looked into Relationship Manager source. With this manager only solution to connect records is below table ? CREATE TABLE RELATIONSHIPS ( OID VARCHAR(36) NOT NULL, FROM_OID VARCHAR(36), TO_OID VARCHAR(36), REL_TYPE INTEGER); With Relationship Manager I have to forget about foreign keys in tables ? -- Regards Jaromir ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk
