-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Zbigniew Lukasiak wrote: > <[EMAIL PROTECTED]> wrote: >> Ideally, DBIC would instead populate the relationship_info >> details after someone has set up >> __PACKAGE__->many_to_many(...). That would avoid this >> guesswork. > > I have been nagging Matt about that for about 3 years (just after > the first release of InstantCRUD), there was a slight chance that > this would be added in 0.8 - but unfortunately it was somehow > missed. So now we need to wait for the 0.9 release I figured as much - which makes sense, as the introspection in DBIC is "just enough to get the work done, and no more." Personally I'm waiting for DBICMoose because I think we'll be able to contribute an "introspection layer" much more easily as a plug-in to that. p.s. I've decided to ship that code I mentioned for m2m. It's only used to filter uninteresting columns from the display, and is not for db updates. The uninteresting columns are replaced with data from the "target" table of the m2m. I'm just updating the tests... - -- Oliver Gorwits, Network and Telecommunications Group, Oxford University Computing Services -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI38zI2NPq7pwWBt4RAqgqAKDWhELgoBii4U4aE27hVQEecY9dqACgvOIe OmNYKzOoAWscWpZF2/S8ApM= =kHHv -----END PGP SIGNATURE----- _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[EMAIL PROTECTED]
