[hibernate-dev] Wishing to work on Hibernate's DDL capabilities

[Francis Galiegue]

2009/6/11 Max Rydahl Andersen <max.andersen at redhat.com>:
> Splitting out dml/ddl so one could build something like a "structural
> compare of configurations" to create a better
> migration would be interesting;

That's one of the aspects I was thinking about when I proposed a
DDL/DML separation. HQL only requires the DML part, after all.

> though I really don't believe dynamic
> mappings that also dynamically decided
> the db-layout and statements is going to be more than a quick prototyping
> tool. i.e. don't go in production with it :)
>

This is what I really want to achieve, though. I'm close to it, really
close. The Dialect API, as it exists today, only lacks a few pieces
and logical separation to make it easier and fully functional. And it
is of high interest for our application, which requires that mappings
be dynamic, with no downtime (POJOs are out of the question for such a
setup, though, or so I believe, since the ability to compile generated
code on the fly is only really integrated with Java 1.6 - but I don't
use POJOs...)

I'll come up with specific questions over the weekend concerning the
existing code (I use 3.3.1), since some parts remain really obscure to
me. I can then come up with proposals, which, I believe, will have to
be JDK 1.4 compliant, right?

-- 
Francis Galiegue, fgaliegue at gmail.com
"It seems obvious [...] that at least some 'business intelligence'
tools invest so much intelligence on the business side that they have
nothing left for generating SQL queries" (Stéphane Faroult, in "The
Art of SQL", ISBN 0-596-00894-5)