cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luca Garulli <l.garu...@gmail.com>
Subject Re: Daisy as CMS: why don't use JDO?
Date Wed, 13 Oct 2004 17:44:44 GMT
On Wed, 13 Oct 2004 16:11:21 +0200, Steven Noels
<stevenn@outerthought.org> wrote:
> On 13 Oct 2004, at 15:17, Ugo Cei wrote:
>
> ... and that's what Daisy query statements eventually get translated
> into: straight SQL-statements and JDBC calls. The Document object model
> might somehow fit into something an O/R tool could map between objects
> and tables, but we wanted to provide an easy, SQL-like query language
> for searches. And in order to be able to tune execution performance of
> the query language, we figured we'd have to do our own mapping as well,
> if only so that we know which performance issues we might encounter,
> and how we should optimize the database scheme in that respect.

Ok, what I'm trying to say is that using JDO you don't worry so much
about persistence theme, optimization, support of N database, etc.

> Don't be too scared about MySQL dependency of Daisy, BTW:
> 
> "Daisy doesn't really depend on any special MySQL features (though a
> database with transaction support and row-level locking is required),
> but it simply wasn't a priority for us to support other databases as
> well."

Ok, but consider the use of JDO for all the aspects of the persistence.

Just my 0,02 € ;-)

-- 
bye,
Luca Garulli
OrienTechnologies.com
(the light ODBMS, all in one JDO solution)

Mime
View raw message