> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Pierre van Rooden
> Verzonden: dinsdag 23 juli 2002 11:37
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: mysql adding indexes
>
>
> Daniel Oceloen wrote:
> > Well the facts are it was added without consultation
>
> Mostly because nobody cares for the Transaction project.
> Actually when I checked it in I did consult the list and explained the
> use, but nobody reacted.
>
Well i don't see how this falls under the transaction project, i do not want to
end up in a fist fight but the result is something only a few people know about.
> > is that its might be supported but not for all databases and
> nobody knows
> > its there.
>
> We're very busy ammending that. :)
>
> > Infact we could say this about the whole Store system.
>
> It is not a system but a Storage interface, an alternate interface for
> JDBC2Node interface, which is too dependent on certain behaviors and
> allows other javacode to carete their own sql statements.
> The storage classes are backwards compatible in design (until we can get
> rid of the old interface, which will probably take a while).
>
And this was also done under the transaction project ?
> > The whole database abstraction is now very unclear and seems to
> > be based on 2 frameworks personally i have no clue how we got
> to this state
> > but we do need to clear this up.
>
> I definetely hope the Query project will use the storage classes - at
> least take their design into account. I think the old classes are really
> bad - ind esigna nd the way they 'inherit' - if that's the word - form
> the other classes.
> I feel quiet confident that it would not be too hard to create (for
> instance) an Informix Storage class. But I can't run Informix so I
> cannot be sure.
>
> > Upto know it was _not_ normal for mmbase to
> > add indexes because people told me it depends alot on the
> database used and
> > is a db admins job, im not against adding it btw.
>
> You can configutre it now and it works, which beats having configuration
> that DOESNT work.
yeah but you seem to jump over the fact that we now have a new database layer designed
inside a project where it imho doesn't fit. Again im not agaist redoing the old system
but
i do think its a good example how easy it is to create something that grows into a
monster
that before we know it replaces a core part of the software.
Daniel.
