+1
On Aug 10, 2012, at 12:38 AM, Steve Ebersole <steve(a)hibernate.org> wrote:
The basics of org.hibernate.service.schema.spi.SchemaManagementTool
are
essentially done. There is a lot of clean up I want to do after
Configuration is gutted or removed, changing how SchemaExport, etc work
internally.
But one thing I wanted to discuss was to change up how Exportable works.
Today, its really not much different than what we used to do. The
database objects themselves know how to render themselves into SQL
CREATE/DROP/ALTER commands. What I am contemplating is externalizing
this rendering (lets call them ExportableRenderer, thought better names
welcome). This would serve 2 useful purposes:
1) Clean up the Table, Sequence, etc code clutter.
2) Allow plugging in alternate renderings for things. This could be
dialects or users or event custom SchemaManagementTool supplied.
WDYT?
--
steve(a)hibernate.org
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio