Comments on: single table inheritance pattern in symfony using propel http://toni.uebernickel.info/development/single-table-inheritance-pattern-in-symfony-using-propel/ a small part of my life Sat, 22 May 2010 14:45:30 +0000 http://wordpress.org/?v=2.9-beta-2 hourly 1 By: havvg http://toni.uebernickel.info/development/single-table-inheritance-pattern-in-symfony-using-propel/comment-page-1/#comment-493 havvg Wed, 20 Jan 2010 09:45:40 +0000 http://toni.uebernickel.info/?p=623#comment-493 Thanks for the advice, Derek. I wasn't aware of such a feature provided by propel. This makes may posting out of date :-) The solution about the type is great, imho! Thanks for the advice, Derek. I wasn’t aware of such a feature provided by propel. This makes may posting out of date :-)

The solution about the type is great, imho!

]]> By: Derek Martin http://toni.uebernickel.info/development/single-table-inheritance-pattern-in-symfony-using-propel/comment-page-1/#comment-492 Derek Martin Tue, 19 Jan 2010 20:58:59 +0000 http://toni.uebernickel.info/?p=623#comment-492 I think you misunderstand Propel's single table inheritance feature. Above, you are not doing single table inheritance. If you do a query using CommentPeer, it will also return rows that are Entries. If you do a query using EntryPeer, it will also return rows that are Comments. This is incorrect. Propel's STI feature says you must add a column to use as a "classkey", and define this in the schema.xml file. For example 1=Entry, 2=Comment. Then when you $comment->save() it will automatically do: $comment->setClassKey(2); first. Also, your technique requires creating a table called Comment, and then abandoning it. Propel's STI feature doesn't require that step. It can automatically generate the Comment classes for you, from the Entry table. Check out the docs here: http://propel.phpdb.org/trac/wiki/Users/Documentation/1.3/Inheritance I think you misunderstand Propel’s single table inheritance feature. Above, you are not doing single table inheritance. If you do a query using CommentPeer, it will also return rows that are Entries. If you do a query using EntryPeer, it will also return rows that are Comments. This is incorrect. Propel’s STI feature says you must add a column to use as a “classkey”, and define this in the schema.xml file. For example 1=Entry, 2=Comment. Then when you $comment->save() it will automatically do: $comment->setClassKey(2); first. Also, your technique requires creating a table called Comment, and then abandoning it. Propel’s STI feature doesn’t require that step. It can automatically generate the Comment classes for you, from the Entry table. Check out the docs here: http://propel.phpdb.org/trac/wiki/Users/Documentation/1.3/Inheritance

]]>