Re: MooseX::FSA::Simple

On 11-09-21 07:24 AM, Moritz Onken wrote: The question is, how would someone name his dist who wants to release a version of FSA::Role, which uses Role::Basic as Role framework? If it inherits from Role::Basic, shouldn't it be named Role::FSA? I think we need something like Any::Role :-)

Re: MooseX::FSA::Simple

On 11-09-19 01:13 PM, Dave Rolsky wrote: That said, another namespace for modules designed to work with other Moose _using_ modules might be useful. No good names come to mind right now, though. How about Rocky? (Because Flying_Squirrel is too long.) https://secure.wikimedia.org/wikipedia/en/w

Re: Newborn MooseX module up for adoption

On 11-08-28 08:15 PM, Jess Odum wrote: I'm not exactly sure what the arguments for "AUTOLOAD considered harmful" are, but I do believe that AUTOLOAD's use should be limited and with responsibility. Name collision is one reason.

Re: Persistent Objects Using SQL

On 10-06-02 12:14 PM, Stevan Little wrote: Primary key and foreign key are meaningless to Moose because that is not how objects connect to one another, that is how you imply relationships in a RDB. I think perhaps you're too stuck in RDB thinking, keys are most certainly not a requirement for a d

Re: Persistent Objects Using SQL

I want to thank all those who responded. Your comments have given me a view of the state of the art as it currently exists. And from what I gather, it sucks. There is a lot of software that stores objects in a RBD and they do a good job. The problem is that while there the models for object

Persistent Objects Using SQL

Hi, Is the a standard methodology for persistent objects in Moose using SQL? I'm writing a small web spider and I want my sites to be persistent objects. Two abilities would be useful: 1. Deferred loading: objects are not loaded unless they're needed. 2. Save on exit if dirty: no need