Re: Two more comments

• To: ozone-users@ozone-db.org
• Subject: Re: Two more comments
• From: Falko Braeutigam <falko@softwarebuero.de>
• Date: Thu, 30 Dec 1999 17:16:34 +0100
• In-Reply-To: <2860395.3155413816@turtlecoral.rem.cs.cmu.edu>
• Organization: SMB
• References: <2860395.3155413816@turtlecoral.rem.cs.cmu.edu>

On Wed, 29 Dec 1999, you wrote:
> Hi,
>   I just ended up with a database with an old version of a class in the
> store.  I had overwritten the class file for it.  Whenever I tried to
> access the object to delete it I would get a ClassCastException.  Would a
> deleteByName() method in Database fix this?
Not really. A ad-hoc tool and/or a garbage collector would be the best
solution to deal with this kind of "leaks". Both is not yet implemented. XML/DOM
seems to be a good foundation for an ad-hoc query tool.

>  That way you might be able
> delete the object without ever having to explicitly reference it.
> 
>   Secondly, I've been working with inheritance between interfaces.  This
> mostly works pretty well, but if you are using comments to specify whether
> a method is an update method then that info is not inherited.
You only need interfaces for the classes that are actually database objects.
There is no need to write interfaces for each sub-class. However, in case you
also want database objects of a sub-class then you must add the inherited
methods to the interface of the super-class. IMO this is ok because it forces
you to describe the entire database interface of the class in the interface.


Falko
-- 
______________________________________________________________________
Falko Braeutigam                         mailto:falko@softwarebuero.de
softwarebuero m&b (SMB)                    http://www.softwarebuero.de

• References:
  • Two more comments
    • From: William Uther <will+ozone-db@cs.cmu.edu>

• Prev by Date: Re: nameObject bug?
• Next by Date: delete
• Prev by thread: Two more comments
• Next by thread: nameObject bug?
• Index(es):
  • Date
  • Thread