Re: Database vs Data Structure?
- From: castironpi@xxxxxxxxx
- Date: Thu, 17 Apr 2008 21:30:33 -0700 (PDT)
On Apr 17, 9:30 pm, erikcw <erikwickst...@xxxxxxxxx> wrote:
Hi,
I'm working on a web application where each user will be creating
several "projects" in there account, each with 1,000-50,000 objects.
Each object will consist of a unique name, an id, and some meta data.
The number of objects will grow and shrink as the user works with
their project.
I'm trying to decided whether to store the objects in the database
(each object gets it's own row) or to use some sort of data-structure
(maybe nested dictionaries or a custom class) and store the pickled
data-structure in a single row in the database (then unpickle the data
and query in memory).
A few requirements:
-Fast/scalable (web app)
-able to query objects based on name and id.
-will play nicely with versioning (undo/redo)
Any input on the best way to go?
Thanks!
Erik
When you change an object, what will you do?
1) Changes on disk only.
2) Changes in memory only & flush.
Databases cache a binary in memory, which I find underrated.
.
- References:
- Database vs Data Structure?
- From: erikcw
- Database vs Data Structure?
- Prev by Date: Re: How to make this unpickling/sorting demo faster?
- Next by Date: Re: Database vs Data Structure?
- Previous by thread: Database vs Data Structure?
- Next by thread: Re: Database vs Data Structure?
- Index(es):
Relevant Pages
|