On 2 Dec 2006, at 15:28, Nilson Santos Figueiredo Junior wrote:
On 12/2/06, Matt S Trout <[EMAIL PROTECTED]> wrote:
First thing: inflating to different classes based on a column
Actually, when selecting it doesn't really inflate to the different
classes. In the table A, table B, view V example above, when selecting
you'd get V objects, not A or B objects.
Right, then what we definitely want is a smarter ResultSource object
- one that produces the appropriate union select when ->from is
called, and can redirect insert/update requests appropriately. the
problem, as I say, is that currently the ResultSet passes the source
straight through to storage whereas what we really need is to be
passing the request to the source first so it can indirect through
sources for tables A and B as appropriate.
Might be worth having a look at John's bytea-related branch and
seeing how much trouble it'd be to do this - then it could be
completely transparent to the class itself ...
--
Matt S Trout, Technical Director, Shadowcat Systems Ltd.
Offering custom development, consultancy and support contracts for
Catalyst,
DBIx::Class and BAST. Contact mst (at) shadowcatsystems.co.uk for
details.
+ Help us build a better perl ORM: http://dbix-
class.shadowcatsystems.co.uk/ +
_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
Searchable Archive: http://www.mail-archive.com/[email protected]/
