durusmail: durus-users: Durus basics
OODB basics
2005-10-08
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-11
2005-10-12
Re: OODB basics
2005-10-11
OODB vs SQL
2005-10-09
2005-10-09
2005-10-09
Re: OODB vs SQL
2005-10-10
Re: OODB vs SQL
2005-10-10
OT: Durus
2005-10-13
2005-10-13
2005-10-13
2005-10-09
2005-10-09
2005-10-09
2005-10-10
2005-10-11
2005-10-11
2005-10-11
2005-10-11
Re: OODB vs SQL
2005-10-11
2005-10-11
2005-10-11
2005-10-12
2005-10-12
2005-10-12
Demo application [was: Re: [Durus-users] Re: OODB vs SQL]
2005-10-13
Re: OODB vs SQL
2005-10-11
Durus basics
2005-10-09
2005-10-09
2005-10-10
2005-10-10
2005-10-10
2005-10-13
2005-10-13
2005-10-13
2005-10-13
Re: OODB basics
2005-10-13
Durus basics
Oleg Broytmann
2005-10-13
Hello!

On Sun, Oct 09, 2005 at 05:49:33PM -0400, David Binger wrote:
> On Oct 9, 2005, at 4:51 PM, Oleg Broytmann wrote:
> >   Can I have a serial (autoincremented) counter? Should I? They
> >are useful
> >in cases when I don't have an interesting distinguishing features
> >in my
> >objects. For example, if I want to store a list of FTP servers I can
> >distinguish them by their URLs; hence I can use URLs as indices.
> >But if I
> >want to store access_log elements - there are no such distinguishing
> >elements. Even the full tuple (time, client IP, URL) can occur many
> >times
> >(many concurrent queries from a program like ApacheBenchmark; or a
> >huge
> >network behind a NAT with a single external IP). Autoincremented
> >counter
> >seems to be the best way to generate names (indices).
>
> I think I would do that as a BTree whose values are Persistent
> instances with a single "int" attribute.

   Keys, not values? Or I've missed something important here...

Oleg.
--
     Oleg Broytmann            http://phd.pp.ru/            phd@phd.pp.ru
           Programmers don't die, they just GOSUB without RETURN.
reply