Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Sean Allen
On Jun 2, 2008, at 9:14 AM, Martijn Faassen wrote: Hi there, Christian Theune wrote: this might be interesting to ZODB users and developers: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/302177093/article.pl What I find interesting is that Python has had such a thing for about a decade

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Sean Allen
On Jun 3, 2008, at 10:52 AM, Martijn Faassen wrote: Hi there, On Tue, Jun 3, 2008 at 3:28 PM, Sean Allen <[EMAIL PROTECTED] > wrote: [snip] i dont think you can compare ZODB to gemstone's products. i've looked at both over the last few months with a decent level of depth and the gemstone

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Lennart Regebro
On Tue, Jun 3, 2008 at 5:28 PM, Sean Allen <[EMAIL PROTECTED]> wrote: > What is different is that persistence is built into their vm. > You just put anything into any global and its persisted. Yeah, that's nice. I want the whole operating system to work like that. ;) -- Lennart Regebro: Zope and

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Martijn Faassen
Hi there, On Tue, Jun 3, 2008 at 3:28 PM, Sean Allen <[EMAIL PROTECTED]> wrote: [snip] > i dont think you can compare ZODB to gemstone's products. i've looked at > both over the last few months with a decent level of depth and the gemstone > from a programmer's standpoint is infintately easier to

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Martijn Faassen
On Tue, Jun 3, 2008 at 5:28 PM, Sean Allen <[EMAIL PROTECTED]> wrote: [snip] > What is different is that persistence is built into their vm. > You just put anything into any global and its persisted. Okay, that's like the PyPy approach and cannot be done really without doing it on the interpreter

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Tim Cook
On Tue, 2008-06-03 at 11:28 -0400, Sean Allen wrote: > if i have customer A who has order B > > and i store customer A to customer dictionary > and order B to order dictionary > > then later access order B from order dictionary, modify and update it > > does ZEO update the instance of order p

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Martijn Faassen
Hey, On Tue, Jun 3, 2008 at 6:09 PM, Tim Cook <[EMAIL PROTECTED]> wrote: [snip] > But that's a feature and not a limitation. :-) > > If I store patient A in demographics > and a clinical entry B in ehr > > When I edit the clinical entry B my DBM had better NOT update B. It is > supposed to create

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Sean Allen
How does Gemstone implement efficient querying or indexing? [snip] Okay, this sounds like an indexing framework built into the database layer, something the ZODB doesn't have, but of course has been built on top with the catalog. pretty much. i haven't looked into the specific details of

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Martijn Faassen
Hey, On Tue, Jun 3, 2008 at 7:32 PM, Benji York <[EMAIL PROTECTED]> wrote: > On Tue, Jun 3, 2008 at 1:13 PM, Gary Poster <[EMAIL PROTECTED]> wrote: >> >> What you *can't* do out of the box is ask "hey, what products have an >> attribute that points to this brand?". That's a back-reference, and th

[ZODB-Dev] What the ZODB really does

2008-06-03 Thread Martijn Faassen
Hi there, The discussion on Gemstone isn't the first time that people seem to think the ZODB doesn't do what it actually does. If you have object A that points to B, and object C that also points to B, updating B will update B truly, and A and C will both aware of this change. Quite a few sm

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Benji York
On Tue, Jun 3, 2008 at 1:13 PM, Gary Poster <[EMAIL PROTECTED]> wrote: > > What you *can't* do out of the box is ask "hey, what products have an > attribute that points to this brand?". That's a back-reference, and that > needs solutions like the ones to which I was referring. In other words: if

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Gary Poster
Uh-oh, I'm implicated! (see below) On Jun 3, 2008, at 12:53 PM, Sean Allen wrote: ... If you do that in gemstone, there is only one copy of Order B, no matter what variable in what dictionary you come at it from. And its drop dead simple. I looked at implementing that with zodb an

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Sean Allen
On Jun 3, 2008, at 1:32 PM, Benji York wrote: On Tue, Jun 3, 2008 at 1:13 PM, Gary Poster <[EMAIL PROTECTED]> wrote: What you *can't* do out of the box is ask "hey, what products have an attribute that points to this brand?". That's a back-reference, and that needs solutions like the ones

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Benji York
On Tue, Jun 3, 2008 at 3:45 PM, Sean Allen <[EMAIL PROTECTED]> wrote: > > On Jun 3, 2008, at 1:32 PM, Benji York wrote: > >> On Tue, Jun 3, 2008 at 1:13 PM, Gary Poster <[EMAIL PROTECTED]> wrote: >>> >>> What you *can't* do out of the box is ask "hey, what products have an >>> attribute that points

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Sean Allen
On Jun 3, 2008, at 1:13 PM, Gary Poster wrote: Uh-oh, I'm implicated! (see below) On Jun 3, 2008, at 12:53 PM, Sean Allen wrote: ... If you do that in gemstone, there is only one copy of Order B, no matter what variable in what dictionary you come at it from. And its drop dead sim

Re: [ZODB-Dev] Re: Ruby/Smalltalk OODB

2008-06-03 Thread Sean Allen
On Jun 3, 2008, at 4:06 PM, Benji York wrote: On Tue, Jun 3, 2008 at 3:45 PM, Sean Allen <[EMAIL PROTECTED] > wrote: On Jun 3, 2008, at 1:32 PM, Benji York wrote: On Tue, Jun 3, 2008 at 1:13 PM, Gary Poster <[EMAIL PROTECTED]> wrote: What you *can't* do out of the box is ask "hey, what pr