in reply to tie::hash files..

What other tehniques i can employ to make things better
That highly depends on your definition of 'better'. Considering your requirement of:
I can edit the files with text editor.
all typical methods to make access or store faster are disqualified.

There really isn't much Perl into this question. The fact that you are using a tied hash as part of the interface hardly matters for the answer - the tied hash is just syntactical sugar, and your question is really about the internal structure of the data file. And considering your requirements, you're most likely going to end up with flat files anyway - including full dumps. Regardless of your choice of implementation language.

You could of course read in all data at program start, and dump it on program termination, but that won't leave much if the required parallel access.

I'd use a SQL database server, where all the problems already have been solved for me. I'd be grateful that it takes away the temptation to modify the data in an editor - although it's not going to prevent me from doing it (most databases will allow you to dump the data of one or more tables to a text-editor edable file, and allow you to read in from such a file as well).

Abigail

Replies are listed 'Best First'.
Re: Re: tie::hash files..
by bugsbunny (Scribe) on Jan 12, 2004 at 15:40 UTC
    hmm.. u are maybe right,

    what I had in mind for "edit with text editor" is not that I have file open for hours, but just quick edits.. (i'm searching to make MC lock/unlock on file/edit<->exit)
    and in most of the cases giving other parties "file is locked, pls try again later" is not a big problem... 'cause the the other "parites" sit next to me :")
    this is mostly a precaution measures..

    SQL is a beast for my current task.
    - need alot of prerequisites
    - hard to move and change frequently
    - will be slower, i think
    will be doing it when i have a clearer picture of the whole thing..
    for now the question is how to make EDITS of FLAT faster ? with perl ofcource :")
    thanx anyway
      what I had in mind for "edit with text editor" is not that I have file open for hours, but just quick edits.
      Indeed. And that limits you a lot. Indices would be out of the question, which means you don't have performance.
      SQL is a beast for my current task.
      - will be slower, i think
      Will be slower than what? A hand-rolled solution in Perl where you lock entire files, and dump the entire data structure on each modification?
      for now the question is how to make EDITS of FLAT faster ? with perl ofcource :")
      Lower your requirements.

      Abigail