Re: Generating SQL

From: Otavio C. Decio (REMOVEodecio_at_earthlink.REMOVE.net)
Date: 11/15/04 

Date: Mon, 15 Nov 2004 06:10:31 -0500

"Topmind" <topmind@technologist.com> wrote in message
news:4e705869.0411141849.4e871928@posting.google.com...
> "Otavio C. Decio" <REMOVEodecio@earthlink.REMOVE.net> wrote in message
news:<vcCdndLJWpilFQjcRVn-3A@giganews.com>...
>
> Scanning a bunch of column descripter classes for column
> info sounds like a kind of data dictionary.

Yes, a data dictionary documented in code - the value object class. Change
the data dictionary means change the class - the SQL gets updated with no
other code change, just the class definition.

>
> Well, anything is wrappable, but that does not necessarily mean
> that it should be wrapped. You may end up inventing a custom
> language that is uglier and/or less documented than SQL.
> I'll take a standardized devil over a custom-rolled devil
> in most cases. If you get hit by a bus and your replacement
> cannot find the documentation for your custom query API,
> they may be in for a lot of
> work. But if you get hit by a bus, there are still plenty
> of SQL books and resources available.

That doesn't make string concatenated SQL any more readable or maintainable.
My original intent was to find a better way to communicate with the
database, to make it more consistent. Now I have something that generates
proper SQL, with parameters and data types derived from my classes. Changes
in the database are documented in code - as you said, the value object class
is the data dictionary, which is great.

>
> Any business app programmer who does not know SQL should
> be fired anyhow. Programmers are a dime-a-dozen these days,
> and if you cannot find one who knows SQL (in addition to
> app language), you must be locked in car.
>

Just because programmers are cheap these days doesn't mean that hiring a
dozen of sql-concatenating of them will be any guarantee of success.

>
> -T-

Otavio

Relevant Pages

  • Re: Generating SQL
    ... a data dictionary documented in code - the value object class. ... >> cannot find the documentation for your custom query API, ... >> of SQL books and resources available. ... >> Any business app programmer who does not know SQL should ...
    (comp.object)
  • ANNOUNCE - Muldis::DB v0.0.0 released, in p5+p6
    ... I am pleased to announce the release of Muldis::DB version 0.0.0 for Perl 5 on CPAN. ... If you want to read all the Muldis::DB documentation that exists now, I recommend doing so in this order: ... Muldis::DB implements a D language as defined by Hugh Darwen and Chris Date, and presents a superior interface for working with the relational model of data, contrasted with SQL. ...
    (perl.dbi.users)
  • RE: Microsoft Jet SQL Reference
    ... The entire Jet 4.0 SQL Reference is on your hard drive in the following ... > I'm quite challenged by the CONSTRAINT clause documentation. ... > CREATE TABLE Orders (OrderId INTEGER PRIMARY KEY, CustId INTEGER, OrderNotes ...
    (microsoft.public.access.queries)
  • Re: argh! more undocumented mysteries: to_yaml
    ... searchable PDF format. ... Page 758 is the description of the YAML standard library. ... Object class, AND it appears in association with MANY other classes. ... When that documentation tells me that it is a method of the Object ...
    (comp.lang.ruby)
  • Re: An efficient way to read data from excel
    ... Do you have some URLs for SQL documentation specific to this task? ... Administrator Drivers tab on my computer? ...
    (microsoft.public.scripting.wsh)