This is a great change, +1.
If you post a diff to JIRA I will take a peek.
drew wills
Eric Dalquist wrote:
I was digging through some Hibernate API docs for another project and
stumbled upon their mapping API. The provide a quite nice API that is
pretty easy to manually create an object model representing a database
Table and then, by passing a Dialect get the SQL for creating/dropping
that table. Building on that I threw together a bit of code to do this
from a uPortal tables.xml file.
What I have now is a replacement DbLoader that uses Hibernate to drop
and create tables and a simplified Spring JDBC backed class for doing
data population. The biggest end-user advantage to this is no more
mucking with mappings in dbloader.xml. We'll also easily be able to
support any database that Hibernate supports as now all of our table
creation SQL is generated by Hibernate. I was also easily able to add
named index support and unique column sets to the tables.xml format,
something we haven't been able to do previously.
I'd like to propose this change for 3.1. It would be backwards
compatible for a 3.0 inclusion but could create confusion with the
documentation since there would no longer be a need for dbloader.xml
mapping but only in 3.0.3 and later.
If folks are interested I can post the diff for th changes.
-Eric
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
