On Mon, Dec 27, 2004 at 07:44:23PM -0800, Peter Speltz wrote:
> > Especially when moniker dosn't seem to be the problem so much as
> > Class::DBI::Loader.
> Neither are the problem in Maypole. The problem is Maypole is using
> $class->moniker as a name of a directory.
That's not the problem. The problem is that moniker is giving the wrong
answer because Loader is setting up the class name wrongly. If Loader
didn't mess with underscores, then the moniker would be the table name.
In the general case here, I believe using moniker() is correct. As
pointed out, table names will not necessarily be safe for directory or
file names on all databases. A class name, from which the moniker is
derived, will be.
All of this confusion has come from the fact that Loader has created
classes with unexpected names.
> . Isn't moniker is meant for human consumption not computer consumption.
I'm not sure where you got that idea, but I wouldn't agree with that.
One of the primary uses of moniker, and certainly the one that led to
its creation, was to allow the computer to make sensible guesses at what
to call other things based on a class name.
Tony
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT