Re: Database Builders, Code Generators, On-Topic?

From: Marshall Spight <mspight_at_dnai.com>
Date: Mon, 26 May 2003 01:58:39 GMT
Message-ID: <jxeAa.735306$Zo.156729_at_sccrnsc03>


"Bob Badour" <bbadour_at_golden.net> wrote in message news:zhcAa.273$uN5.72058913_at_mantis.golden.net...
> "Kenneth Downs" <MyUseNetHandle_at_linuxmail.org> wrote in message
> news:e3arab.kkk.ln_at_mercury.downsfam.net...
> > We
> > use this to generate both DDL at install time and DML at run-time, and
> also
> > client code (pure under-the-hood, nothing cosmetic).
>
> Sounds fair enough. Does it handle schema version upgrades? ie. Does it
> generate the DDL to update one schema versionb into a new schema? If so,
> does it do this without data loss?

These are the sorts of questions I'd love to hear discussed.

> > I have not seen this discussed here much, and wonder if such discussions
> are
> > welcome. If not, is there a more appropriate forum?
>
> The only other candidate would seem to be comp.databases, and I have no
> opinion on which of the two is more appropriate.

Seems like that group's mostly about how to back up mysql. :-)

> > In an effort to give some rigor to our design strategies, I have coined
> [1]
> > the term "Scalar Complete" to refer to the insistence that all meta-data
> be
> > composed entirely of scalars, meaning that meta-data must never be an
> > expression that is evaluated according to the syntax rules of a language
> > (the expression "price * qty" may look like passable scalar data, but it
> is
> > not), and must never require parsing.
>
> I fail to see how that arbitrary restriction provides rigor. It sounds more
> like a "Gee, my life as implementer would be easier..." kludge.

Gotta agree. What's the advantage?

> Paul Vernon seems to have an interest in devising a
> standard relational system catalog.

He does? So do I.

Marshall Received on Mon May 26 2003 - 03:58:39 CEST

Original text of this message