The Artima Developer Community
Sponsored Link

Python Buzz Forum
Schevo and Durus

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Ian Bicking

Posts: 900
Nickname: ianb
Registered: Apr, 2003

Ian Bicking is a freelance programmer
Schevo and Durus Posted: Mar 30, 2005 10:43 AM
Reply to this message Reply

This post originated from an RSS feed registered with Python Buzz by Ian Bicking.
Original Post: Schevo and Durus
Feed Title: Ian Bicking
Feed URL: http://www.ianbicking.org/feeds/atom.xml
Feed Description: Thoughts on Python and Programming.
Latest Python Buzz Posts
Latest Python Buzz Posts by Ian Bicking
Latest Posts From Ian Bicking

Advertisement

I saw two presentations on the second day of PyCon which interested me in combination, one on Schevo and another on Durus. I've always been reluctant about object databases. ZODB... well, it works, and I'm sure it works well -- I haven't really had problems -- but it doesn't make me feel safe.

This isn't because of integrity or stability issues as much as data stability, portability, upgradability, queriability (is that a word?) I want to be able to ask questions about my data (like, say, how many people registered in a certain date range), questions that I didn't think about when I was setting up my data. And I want to control how my data changes as my application and the data itself evolves; generally it should be easy, and it should always be possible -- ALTER TABLE and other operations (like multi-record UPDATE) mostly do that well in an RDBMS.

Schevo is a fairly restricted object model built on top of a database. It builds indexes and relations and maintains integrity for you, and seems to have some conventions to control upgrades. These are all the aspects of an RDBMS that I care about... well, at least most of the things I care about.

Schevo is really just the schema -- it builds on top of an object database (Pypersyst, Durus, or ZODB). Which is where Durus comes into play -- Durus is kind of a simpler reimplementation of ZODB. The only real way that ZODB sounded better was that it's threadsafe, so you can run it in process in a threaded environment. But Durus is client-server -- like ZEO (the client-server extension to ZODB) -- and that's good enough for me.

I like an RDBMS for many of its practical advantages -- it's really good infrastructure. But I'm not in love with them. I want data that can last for years and across systems; that doesn't have to be an RDBMS. Right now that's practically the only good option -- XML persistence is another option, or some other simple flat-file systems, but those are painful to work with. I still don't feel good about object databases, but at least this feels like a move in the right direction.

Read: Schevo and Durus

Topic: The Battle of the Less Clueless Previous Topic   Next Topic Topic: you_smell.py

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use