On Wed, 2005-10-26 at 00:06 +0100, David Baird wrote: > On 10/25/05, Aaron Trevena <[EMAIL PROTECTED]> wrote: > > On 10/25/05, Jim Mintha <[EMAIL PROTECTED]> wrote: > > > A good example (and my question for this mail). I want to override > > > the column_type procedure (some of the varchar fields from oracle I > > > would like as textareas) If I create something like: > > > [...] > > > > I would like to update the API so that you can specify the column > > types in your controller much in the same way as Package->untaint is > > used. > > I like this suggestion a lot. I liked Peter's idea from long ago to > define custom column_type() methods in individual model classes, this > would save you the trouble and it's good to bring config data back to > the driver.
Yes, but does it create circular dependencies? Does it make it easier or harder to use the model by itself with a command-line script, for example? I can see arguments that the information belongs in the (non-Maypole) model (e.g. that's what you did with CDBI-FB vs M-FB), I can see arguments that some info belongs in the presentation (i.e. Maypole model or view). I could see arguments for a separate static configuration module. But I don't see a good argument that it belongs in the driver - I think it's just being used as a catch-all. Cheers, Dave ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Maypole-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-users
