From: Gavin K. <ga...@ap...> - 2002-11-08 13:45:44
|
Has everyone seen this: http://66.218.140.50/tac/index.html Its a tool to reverse engineer Hibernate mapping documents from the database. Very nice (and a nice Swing UI.) |
From: Daniel B. <db...@bi...> - 2002-11-08 22:28:35
|
Awesome! I just pointed it at a MySQL database I had here and it worked great. Can't wait to see it cleaned up and put into CVS I might try it against some more complex schema at work next week. Can we move towards the "best practise" of having one mapping per class maybe? Gavin King wrote: >Has everyone seen this: > >http://66.218.140.50/tac/index.html > >Its a tool to reverse engineer Hibernate mapping documents from the >database. Very nice (and a nice Swing UI.) > > > > >------------------------------------------------------- >This sf.net email is sponsored by: See the NEW Palm >Tungsten T handheld. Power & Color in a compact size! >http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en >_______________________________________________ >hibernate-devel mailing list >hib...@li... >https://lists.sourceforge.net/lists/listinfo/hibernate-devel > > > |
From: Gavin K. <ga...@ap...> - 2002-11-08 23:49:45
|
> Can we move towards the "best practise" of having one mapping per class > maybe? Yeah, I already requested that (theres a thread in the forum). P.S. Do I spell practice right? Should it be a 'c' or an 's'? I don't care about US-style spelling or whatever, but there are two words, right, a verb and a noun. Am I spelling the noun like the verb? |
From: Andrea A. <aa...@li...> - 2002-11-09 14:43:04
|
On Friday 08 November 2002 23:48, Gavin King wrote: > > Can we move towards the "best practise" of having one mapping per class > > maybe? > > Yeah, I already requested that (theres a thread in the forum). > But why is a best practice? One file per class requires, say, ten open editors to have a look at the whole mapping (A refers a B class, what is it?... we'll, let's open B.hbm.xml) and moreover you have more code to write... Frankly I just see disadvantages in having more than a single mapping file... Best regards Andrea Aime |
From: Gavin K. <ga...@ap...> - 2002-11-11 10:03:12
|
Theres a couple of considerations: * When theres a large number of persistent classes, a single mapping document becomes way to large, unmanageable and virtually impossible to navigate. ie. the same reason why we don't define all our Java classes in one big file. Plus, it keeps the mapping right there in the same directory as the mapped class - easy to find and manage. I have had bad experiences with things like the monolithic struts-config.xml * In a team environment, multiple files tends to interact much better with version control systems (not so much in the case of CVS, but certainly with envy or any system based on locking). Gavin ----- Original Message ----- From: "Andrea Aime" <aa...@li...> To: "Gavin King" <ga...@ap...>; "Daniel Bradby" <db...@bi...>; <hib...@li...> Sent: Sunday, November 10, 2002 2:41 AM Subject: Re: [Hibernate] Tom Cellucci's database reverse engineering tool > On Friday 08 November 2002 23:48, Gavin King wrote: > > > Can we move towards the "best practise" of having one mapping per class > > > maybe? > > > > Yeah, I already requested that (theres a thread in the forum). > > > > But why is a best practice? One file per class requires, say, ten open editors > to have a look at the whole mapping (A refers a B class, what is it?... > we'll, let's open B.hbm.xml) and moreover you have more code to write... > Frankly I just see disadvantages in having more than a single mapping file... > Best regards > Andrea Aime > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > hibernate-devel mailing list > hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel |
From: Christoph S. <ch...@mc...> - 2002-11-11 09:42:53
|
Hey Gavin! ----- Original Message ----- From: "Gavin King" <ga...@ap...> To: "Daniel Bradby" <db...@bi...>; <hib...@li...> Sent: Saturday, November 09, 2002 12:48 AM Subject: Re: [Hibernate] Tom Cellucci's database reverse engineering tool > > > Can we move towards the "best practise" of having one mapping per class > > maybe? > > Yeah, I already requested that (theres a thread in the forum). > > P.S. Do I spell practice right? Should it be a 'c' or an 's'? I don't care > about US-style spelling or whatever, but there are two words, right, a verb > and a noun. Am I spelling the noun like the verb? I think you can spell both the verb and the noun with 's' or 'c' see http://www.m-w.com regards chris > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > hibernate-devel mailing list > hib...@li... > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > |
From: Gavin K. <ga...@ap...> - 2002-11-11 09:58:02
|
> I think you can spell both the verb and the noun with 's' or 'c' Thanks for clearing that up :) I was playing with your SchemaUpdater today (getting it working as a commandline tool). I made a change to get it working with DB2 that I'm not too happy about: I had to change the schema name to "%" instead of the userName. Anyway, have a look and tell me if you can think of any better idea. Gavin |