2008/3/14, Gerardo Herzig <[EMAIL PROTECTED]>: > > Saideep A V S wrote: > > >Hello Sir, > > > > Thank You a ton. I was looking for this function. As far what I've > >understood from the "Shelve" module is that, there would be no memory > >wastage and the whole transactions would be done from and to the file we > >specify. Am I right?. > > > > My actual task is to build a basic dictionary for two languages and > store > >word and its meaning in another language in a file and must be able to > >access it through on-disk Hash tables. as these would be saving memory > space > >for a huge data. > > > >so, I hope shelve is the right one, I am searching for., I shall try out > >with the function. > > > > > >Thank You once again. > > > >Cheers, > >Saideep > > > > > > > Plz remember allways reply to the python group also. They are many many > many ones to know more than i do! > Well, i dont quite think that it would be "no memory wastage", since > when you read/write from disk, there is memory involved in the process. > > I *really* believe that, when data goes huge, a *real* database (like > postgres, and others) has to come and play the game. > > Hope that helps > > Gerardo > > > > -- > http://mail.python.org/mailman/listinfo/python-list >
I'm not sure if a well-written file/seek/read algorithm is faster than a relational database... sure a database can store relations and triggers and all that, but if he's just doing a lookup for static data, then I'm thinking disk IO is faster for him? not sure
-- http://mail.python.org/mailman/listinfo/python-list
