<quote who="Jamie Honan"> > What you've described as wanting is probably an RDBM like MySQL or > Postgres.
Or perhaps Interbase, which was designed for embedded use as well as your standard server style stuff. It feels a bit wrong using a massive hulk of a thing like MySQL or Postgres for what's essentially logging. > How much persistency do you want, how much concurrancy do you want? > Can it be achieved by writing transactions out to a log? (Do you > need to do this anyway? Oh by the way, make sure the log writing > is atomic) Interesting project related to these questions: http://sourceforge.net/projects/prevayler/ > A point I guess I'm getting to is that the database may be underkill as > much as overkill, i.e. not enough to secure your transactions - like if > lots of money depended on it. > > At another extreme, if you wanted to have a free text searching system > with real time updates, or a picture searching system I think you'd need > something else. Annoyingly enough, I have two projects that need ready-to-wear database stuff at the moment; one requires a minimal data store that can handle indexing and multiple writers. The other needs to be a hierarchical data store, and may require full text searching in the future. I'm trying very hard to push these features away onto software that can handle them, but separating the data is going to prove troublesome (I will probably have to lock resources in a server in front of all this data shenanigans). Crazy stuff. > Horses for courses. Or hobby horses. ;-) - Jeff -- "The postmodern version is: If all you have is duct tape, everything starts to look like a duct. Right. When's the last time you used duct tape on a duct?" - Larry Wall -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
