> I'll probably end up using ActiveRecord. I just get caught up
> sometimes in the memory game, and hate seeing my memory usage sky
> rocket as I pull large results. But if I have the memory, why not use
> it to my advantage!
If the situation is something like having an application that only
r
On 1/27/07, James <[EMAIL PROTECTED]> wrote:
> [...]
> I'll probably end up using ActiveRecord. I just get caught up
> sometimes in the memory game, and hate seeing my memory usage sky
> rocket as I pull large results. But if I have the memory, why not use
> it to my advantage!
This is one of th
On 1/28/07, Michael Daines <[EMAIL PROTECTED]> wrote:
> I'm interested in how one can skip the database altogether, though.
> This seems like something that must have come up here before? But
> personally, I threw together a little number I like to call
> DirectoryModel[1] that just keeps track of
> Running a full-featured client/server SQL database engine for
> applications that have only a handful of users is often overkill.
Agreed -- I think this is one of the reasons why pushes SQLite so much
and makes it the default DB engine for Camping. I've started hearing
things about Kirbybase (h
> I tend to use YAML::Store as a sort of poor-man's database for simple
> apps like that. There's also a module called 'fsdb' I used for a
> couple of projects which, IIRC, uses a one-file-per-object model for
> persistent storage.
Wish I'd taken the time to look around... I have certainly
imple
On 1/29/07, Eric Mill <[EMAIL PROTECTED]> wrote:
> > Running a full-featured client/server SQL database engine for
> > applications that have only a handful of users is often overkill.
>
> Agreed -- I think this is one of the reasons why pushes SQLite so much
> and makes it the default DB engine fo
6 matches
Mail list logo
