> Jukka Zitting wrote: > Improvements in the way an underlying database is used are of course > welcome, but in the big picture I don't like having the database being > a driving factor in Jackrabbit design. The way I see it we should be > moving further away from relational databases, towards a native > hierarchical storage model. > > I don't want Jackrabbit using a database, I want Jackrabbit *being* > the database!
Jukka, as a programmer I totally agree with you...but, I am very sure, management won't. Obviously, it are political reasons. Potential (large) customers aren't departing from there oracle infra structure and firing some oracle specialists because they are moving to Jackrabbit. No, they won't move to Jackrabbit *if* Jackrabbit cannot store it in oracle. I do not know the ins and outs obviously, since I am not a salesman (and I do not want be one :-) ), but I am pretty confindent that moving away from databases would imply loosing big potential customers (and companies interested in developing Jackrabbit). So, as a programmer I love your idea, but in the end, it would only harm Jackrabbit a lot AFAICS. Regards Ard > > BR, > > Jukka Zitting >
