On 25 Jun 2007, at 16:52, Ovid wrote: [snip] > Out of curiosity, why rely on the loader?
Because it gets it right (for my particular definition of "right" :-) with no work on my part, and persisting the generated code would be work and YAGNI. > I hope you're not doing this to load all of your classes at runtime! Just the once - persistent process. > I use them to generate template classes, but then I heavily modify > them to present a more OO interface. Thus, later if I want to > change anything in my DB, I'm not locked into the what the loader > is creating each time things get launched. I've got a layer above the generated stuff that has my magic sauce in. I dislike tweaking generated code directly since I usually find that I want to regenerate it again at some point. For example with the apps I'm playing with we've rejigged the schema quite severely a couple of times. Generating them adds a one-off startup cost - but that's not an issue for me at the moment. If it becomes one I'll automate generating the stuff and cache the results. Curiosity satisfied ? :-) Adrian ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
