I agree that concentrating on best practices is a good thing and I know that having composite keys in a database is not regarded as best practice. So I'll probably write my own hybernate template, this gives me the maximum flexibility with all the odds of our aged database.
Andreas Patrik Nordwall wrote: > > ... > The reason for not having a separate DB model is as you mention > simplicity. Sculptor doesn't aim at supporting any type of mapping and > design. It is based on some assumptions, limitations, design best > practices, or whatever you prefer to call it. I think this is a good > thing. General purpose is not always a good thing. > > Ok, how to solve your specific problem? > > Can you add surrogate keys (id columns) in your database schema? > > It is probably possible to create new code generation templates for > Hibernate and DDL which can support natural keys as database > primary/foreign keys, but probably with limitations. > > /Patrik > > > -- View this message in context: http://www.nabble.com/-Sculptor--column-names-for-existing-database--tp15177242s17564p15481223.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
