Re: Update with keeping configuration

Joe,

Thanks for the extensive answer. I'm a java programmer myself.
I haven't used Hibernate before, but I heard good stories.
HSQL is my choice of database for proof of concepts. Easy and it
always works.

My specific point was if you put all this data like flow in the
.albums section there does not seem like a lot of data has to be
persisted in hqsl.

You say it is a good point hsql has a no GPL. Why is that good? btw
hiberbate has the LGPL. Is that not a problem?

And once again thanks for the fine product and bugfixes of 3.13

Ronald


I'm a java programmer myself so I 
> 
> Ronald,
> 
> I'll break that question into two parts: why use ORM (Object
> Relational Mapping), and why use Hibernate/HSQLDB
> 
> Pixory is written in Java, which is an Object Oriented Language. The
> ideal persistence mechanism for an OOL would be an Object Oriented
> Database, because that would allow the plain old java "domain" objects
> that are at the heart of the system to be "magically and
> transparently" persisted. In other words, you would not have a lot of
> programmatic overhead associated with translating between the run-time
> domain objects and the mechanisms of storing and retrieving their
> persistent state. However, when I started project Pixory, over 2 years
> ago, I could not find any open source, java, object database that
> looked ready for prime-time. Even if I had, I personally have no
> experience with object databases and I would have been hesitant to
> adopt an unknown for the heart of the project.
> 
> You can approximate (sort of) an object database with an ORM (Object
> Relational Mapping) framework. When I started Pixory, the decision was
> a no brainer:
> 
> 1) I had been using ORM frameworks since 1996
> 2) The technology is fairly mainstream and very mature. TopLink has
> been around since the early 1990s (in Smalltalk).
> 3) I had been using RDBMs since the early 1990s.
> 4) SQL databases are standardized, so I could substitute different
> implementations.
> 5) SQL databases are well understood, and have lots of third-party
> tools for browsing, etc.
> 
> So the combination of ORM/RDBMS was natural for me.
> 
> Specifically, why Hibernate? I had never used Hibernate before, but I
> liked the design. The design (from the user side) was simpler, lighter
> than NeXTs EOF or Cayenne. It more closely resembled TopLink, which I
> liked for its simplicity. Also, I tested Hibernate extensively, and it
> seemed to always do what the documentation said it should do. So even
> though there were lots of open source, ORM java projects at the time,
> I thought that Hibernate had the highest quality.
> 
> Why HSQLDB? It seemed to work without any problems, and it was the
> only open source, java, SQL, database designed for embedding, that had
> a non-GPL license ;)
> 
> regards,
> 
> joe
> 
> 
> --- In [email protected], "rpu43" <rpu43@y...> wrote:
> > 
> > Thx for the answers about the persistancy stuff, makes sense.
> > Next question arises:
> > Why use HSQL en hibernate at all?
> > 
> > Ronald





------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/EGnolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/pixory-beta/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/