very simple. that doesn't work well with rosedb,
but no problem - i have a filter step that i use to personalize session
data against info from the DB (without getting deep into why, one project
i have is really db heavy, so i precache a lot of generic queries into
memcached with a 5minute
Wow. I'm starting to really like the way you've got this setup. Nice
work, and i owe you a drink (or three)
I'm wondering what the normal 'layout' is for files / packages under
mod_perl
I'm using this right now:
MyLib/
MyLib/RoseDB.pm [ our ISA=
Hm...
It seems a bit tricky to keep things nice and subclassed as I want.
I was hoping on doing something like:
MyObj
MyObj::Manager
MyObj::Cached
but what I've realized is that do handle the cached, I'd need something
like-
MyObj
MyObj::Manager
MyObj::Cached
MyObj::Cached::Manager
or
M
On May 23, 2006, at 3:52 PM, John Siracusa wrote:
The benefits of having a Manager for a ::Cached class are dubious.
Unless you plan to save() (or remember() or forget()) some of the
objects returned by the Manager, it doesn't really matter whether the
Manager's object_class is ::Ca
Hi all,
Never used Rose::DB before, but I've heard enough good things about it
that I'm giving it a try. Some of what I'm writing is probably clunky,
so pointers welcome.
I'm trying to provide my own metadata class and I've run into a problem
I don't quite understand. Here's my base class:
p
Irrelevant side note:
> __PACKAGE__->meta->setup(
> table => 'os',
> columns => [
> os => {
> type=> 'varchar',
> length => 31,
> primary_key => 1,
> not_null=> 1
> },
> type
