Decoupling code from schema

Posted in 1992

Walt Hultgren {rmy} — Mon, 17 Feb 92 15:50:34 -0500 — source: Informix-list mailing list archive (1991-1998)

Path: emory!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!think.com!mintaka.lcs.mit.edu!spdcc!dirtydog.ima.isc.com!ispd-newsserver!kodak!music!amiano From: amiano@music.Kodak.COM (Mitch Amiano) Newsgroups: comp.databases.informix Message-ID: <1992Feb17.152204.26268@kodak.kodak.com> Date: 17 Feb 92 15:22:04 GMT References: <wemhoff.697427191@judy.cs.iastate.edu> <10087@gollum.twg.com> <1678DC164.M22367@mwvm.mitre.org> Sender: amiano@music (Mitch Amiano) Organization: Eastman Kodak Co., Rochester, NY From the SQL vs 4GL thread, I am reminded of my own efforts to reduce the redundant descriptions of the data schema in program variable definitions. I recall reading a few articles in Inforgen's newsletter subject of decoupling the database structure from the code, with a technique using views. My own efforts in this area indicate that it would not be at all unreasonable to put together a set of utilities and a development environment which could eliminate almost all such dependancies ( the dependancies being resolved at compile time ). Has anyone else out there taken this route ? To what extent was it successfully applied ? ---------------------------------------------------------------------------- | Mitch Amiano Current Work Phone: 716-477-3506 | | Software Contractor Address: amiano@music.kodak.com | | Rochester, NY | | 716-226-2024 | ----------------------------------------------------------------------------