Re: persistent composites

On Fri, 19 Jun 2009 15:56:04 +0100, Aaron Brady wrote: This is a welcome digression for me. I wasn't sure that my idea was being taken seriously. On a temperature scale from freezing to boiling, I took Rhodri's message to be somewhere in the single digits-- quite chilly. Correctly, though

Re: persistent composites

On Jun 19, 7:00 am, "Rhodri James" wrote: > On Fri, 19 Jun 2009 14:24:34 +0100, Aaron Brady   > wrote: > > > You are not being any help, Rhodri, in your question. > > To you, perhaps not.  To me, it has at least had the effect of making > what you're trying to do (write a pythonic object database

Re: persistent composites

On Jun 19, 7:45 am, a...@pythoncraft.com (Aahz) wrote: > In article > , > Aaron Brady   wrote: > > > > >You are not being any help, Rhodri, in your question.   > > Maybe not, but honestly, you're getting pretty close to going back in my > killfile.  Although you're no longer trolling this group, I

Re: persistent composites

In article , Aaron Brady wrote: > >You are not being any help, Rhodri, in your question. Maybe not, but honestly, you're getting pretty close to going back in my killfile. Although you're no longer trolling this group, I find your writing difficult to read at best; answering questions from pe

Re: persistent composites

On Fri, 19 Jun 2009 14:24:34 +0100, Aaron Brady wrote: You are not being any help, Rhodri, in your question. To you, perhaps not. To me, it has at least had the effect of making what you're trying to do (write a pythonic object database) clearer. -- Rhodri James *-* Wildebeest Herder to t

Re: persistent composites

On Jun 17, 3:53 pm, "Rhodri James" wrote: > On Wed, 17 Jun 2009 16:06:22 +0100, Aaron Brady   > wrote: > > > > > On Jun 16, 10:09 am, Mike Kazantsev wrote: > >> On Tue, 16 Jun 2009 06:57:13 -0700 (PDT) > > >> Aaron Brady wrote: > >> > Making the charitable interpretation that this was the exten

Re: persistent composites

On Wed, 17 Jun 2009 16:06:22 +0100, Aaron Brady wrote: On Jun 16, 10:09 am, Mike Kazantsev wrote: On Tue, 16 Jun 2009 06:57:13 -0700 (PDT) Aaron Brady wrote: > Making the charitable interpretation that this was the extent of c-l- > py's support and enthusiasm for my idea, I will now go in

Re: persistent composites

On Jun 16, 10:09 am, Mike Kazantsev wrote: > On Tue, 16 Jun 2009 06:57:13 -0700 (PDT) > > Aaron Brady wrote: > > Making the charitable interpretation that this was the extent of c-l- > > py's support and enthusiasm for my idea, I will now go into mourning. > > Death occurred at oh-eight-hundred.

Re: persistent composites

On Tue, 16 Jun 2009 06:57:13 -0700 (PDT) Aaron Brady wrote: > Making the charitable interpretation that this was the extent of c-l- > py's support and enthusiasm for my idea, I will now go into mourning. > Death occurred at oh-eight-hundred. Rest in peace, support & > enthusiasm. I've read this

Re: persistent composites

On Jun 15, 4:56 pm, Aaron Brady wrote: > On Jun 15, 11:10 am, Paul Rubin wrote: > > > Aaron Brady writes: > > > > A real-world application of persistent data structures can be found > > > > here: > > > >http://stevekrenzel.com/persistent-list > > > > Jaime, thanks

Re: persistent composites

Aaron Brady writes: > > A real-world application of persistent data structures can be found here: > > http://stevekrenzel.com/persistent-list > > Jaime, thanks for the link. I contacted its author. You might also look at www.couchdb.org . -- http://mail.python.org/mailman/listinfo/python-list

Re: persistent composites

On Jun 15, 11:10 am, Paul Rubin wrote: > Aaron Brady writes: > > > A real-world application of persistent data structures can be found here: > > >http://stevekrenzel.com/persistent-list > > > Jaime, thanks for the link.  I contacted its author. > > You might also loo

Re: persistent composites

On Jun 15, 8:37 am, a...@pythoncraft.com (Aahz) wrote: > In article <79mtt7f1r480...@mid.uni-berlin.de>, > Diez B. Roggisch wrote: > > >Aaron Brady wrote: > > >> Some time ago, I recommended a pursuit of keeping 'persistent > >> composite' types on disk, to be read and updated at other times by >

Re: persistent composites

On Jun 14, 10:18 am, Jaime Fernandez del Rio wrote: > On Sun, Jun 14, 2009 at 4:27 PM, Aaron Brady wrote: > > > Before I go and flesh out the entire interfaces for the provided > > types, does anyone have a use for it? > > A real-world application of persistent data structures can be found here: >

Re: persistent composites

On Jun 15, 5:45 am, "Diez B. Roggisch" wrote: > Aaron Brady wrote: > > Hi, please forgive the multi-posting on this general topic. > > > Some time ago, I recommended a pursuit of keeping 'persistent > > composite' types on disk, to be read and updated at other times by > > other processes.  Databa

Re: persistent composites

In article <79mtt7f1r480...@mid.uni-berlin.de>, Diez B. Roggisch wrote: >Aaron Brady wrote: >> >> Some time ago, I recommended a pursuit of keeping 'persistent >> composite' types on disk, to be read and updated at other times by >> other processes. Databases provide this functionality, with the

Re: persistent composites

Aaron Brady wrote: > Hi, please forgive the multi-posting on this general topic. > > Some time ago, I recommended a pursuit of keeping 'persistent > composite' types on disk, to be read and updated at other times by > other processes. Databases provide this functionality, with the > exception th

Re: persistent composites

On Sun, Jun 14, 2009 at 4:27 PM, Aaron Brady wrote: > > Before I go and flesh out the entire interfaces for the provided > types, does anyone have a use for it? A real-world application of persistent data structures can be found here: http://stevekrenzel.com/persistent-list Jaime -- (\__/) ( O

Re: persistent composites

On Jun 14, 8:24 am, Steven D'Aprano wrote: > Aaron Brady wrote: > > Some time ago, I recommended a pursuit of keeping 'persistent > > composite' types on disk, to be read and updated at other times by > > other processes.  Databases provide this functionality, with the > > exception that field typ

Re: persistent composites

Aaron Brady wrote: > Some time ago, I recommended a pursuit of keeping 'persistent > composite' types on disk, to be read and updated at other times by > other processes. Databases provide this functionality, with the > exception that field types in any given table are required to be > uniform.

Re: persistent composites

On Jun 14, 3:27 pm, Aaron Brady wrote: > Hi, please forgive the multi-posting on this general topic. > > Some time ago, I recommended a pursuit of keeping 'persistent > composite' types on disk, to be read and updated at other times by > other processes.  Databases provide this functionality, with

persistent composites

Hi, please forgive the multi-posting on this general topic. Some time ago, I recommended a pursuit of keeping 'persistent composite' types on disk, to be read and updated at other times by other processes. Databases provide this functionality, with the exception that field types in any given tabl