i don't know a better way to phrase this, so let me illustrate in
pseudocode
stored_information # base table for stored info
id
useraccount_id
stuff
stored_information__name# extends stored info for name specific
stuff. essentially an 'inherits'
s
On Aug 2, 2006, at 1:47 PM, John Siracusa wrote:
> * Add a has_loaded_related() helper method.
+100
> You should never dereference an object as a hash in end-user code, and
> you should only do so in your own RDBO-derived classes when dealing
> with new attributes that you defined yourself in t
On 8/2/06 3:38 AM, Jonathan Vanasco wrote:
> as-is though, rose is a bit odd -- you can't really loop the same
> object 2x in code if there's a delete
Well, you can always splice the list yourself, which has the advantage of
being more explicit and clear to a reader:
my $bars = $foo->bars; #
On Aug 1, 2006, at 8:27 PM, John Siracusa wrote:
> Ah, gotcha. But how would the functionality you describe be
> implemented?
> You want a method call on an object that's part of a list being
> iterated
> over to cause that object to delete itself from the list. That's
> pretty
> spooky be
