Re: Persistence


frebe73@xxxxxxxxx wrote:

Why do you think OODB never succeeded?

With structured data, it makes more sense to store components in a
flexible way rather than complex assemblies, aka objects. That way you
can use the same data store to support alternate assemblies, from
objects implemented in a programming language to XML documents
communicating between business processes. With unstructured or
semi-structured data, e.g. a DocBook document, it probably makes sense
to store the entire assembly.

Aside from that, many OODB databases were tied to a particular
language, such as C++ or smalltalk. As well, most of the products
never got around to sorting out all the issues with integrity,
transactions, failover, replication, etc.

Regards,
Daniel Parker

.

Relevant Pages

  • Re: OleDb Connection to XML File
    ... This Job object could have a collection ... or writting Jobs as assemblies that the executing assembly dynamically loads ... connect to an XML file with OLE DB. ... would be best to store it in a database-like storage area. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: How to create a new object.
    ... If I store the fullName instead of Type itself it worked fine. ... Will loading all the assemblies before trying to create the object cause any ... "James Curran" wrote: ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Method info discovery using Reflection, variable argument list
    ... >> I'm developing a console app that loads dll assemblies at run time. ... spec then i store the method name. ... I will also store the ParamTypes array ...
    (microsoft.public.dotnet.languages.csharp)
  • Program [representation] database based on OODB?
    ... I'm looking for examples that demonstrate the use of an OODB to store ... I am aware that many Smalltalk systems have integrated program databases ... program database. ...
    (comp.lang.smalltalk)
  • Re: Passing Data Between Assemblies
    ... If the assemblies are in the same process then you can could ... > store it so that assembly B can access it without actually "passing" the ... > Reason why I am not storing the Connection String inside the App.config is ... > to pass this information into the business logic layer and then into the ...
    (microsoft.public.dotnet.languages.csharp)