On Tue, Aug 19, 2008 at 11:31 AM, Ola Bini <[EMAIL PROTECTED]> wrote:
> Hi friends,
>
> It's time to get a full Hibernate implementation in working order, so that
> is what I'm going to start work on tomorrow morning. Aim: focused
> development until I have something that can be used to implement a
> non-trivial database backed application.
> Before I get going, I meant to ask the list if there's anything specific to
> keep in mind, features people would like and so on.
>
> There are also some open questions:
>
> - should it in fact be Hibernate or JPA?
If it doesn't matter too much implementation-wise and doesn't make it
more difficult for the user, JPA would seem to allow for more backend
possibilities, plus tie-ins to EJB.
> - how close should it be to the ActiveRecord API?
If a key use case is to be used with Rails, I think it should at least
have an ActiveRecord-like API, otherwise it will probably feel out of
place.
> - should there be any feature for migrations?
Maybe, leave it TBD or based on feedback. Does Hibernate support any
similar concept you could leverage?
> If I don't get any good conclusions from the list I'll proceed with what
> feels best in my opinion (so you are now officially warned).
One other possibility to mention is to consider writing a DataMapper
backend for it. Might be a fairly quick project, as it appears that
DataMapper backends are considerably smaller than ActiveRecord
adapters. Downside is the higher degree of overlap between DataMapper
and Hibernate infrastructure.
/Nick
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
