Re: "multi-type" where clause

From: Joe Celko (jcelko212_at_earthlink.net)
Date: 04/20/04 

Date: Tue, 20 Apr 2004 10:13:26 -0700

You need to read a book on basic software engineering.

You got a procedure that is under the control of any user at run time.
This is like giving a teenage boy Whiskey and car keys.

You don't know the parameters in the procedure. You don't know the
predicate in the procedure. You have no idea what the datatypes are.
You don't know which columns will come back (SELECT * is dangerous in
production code).

Quick heuristic: You ought to be able to name a procedure with a simple
"<verb><object>" phrase, like "EditForm1107" and then you ought to know
the inputs and outputs.

If you have to make a compound or complex sentence to name it, the
procedure probably lacks cohesion. If you don't know what inputs and/or
outputs are, then it is not actually a procedure at all.

--CELKO--
 ===========================
 Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
schema are.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Relevant Pages

  • Re: make-table query
    ... because there is little or no control over the datatypes used. ... Table query, and gives superior results. ... Tom Ellison ...
    (microsoft.public.access.queries)
  • Re: Formatting a Combo box
    ... fieldnames, datatypes, a record or two of sample data for the first ... Control Source: fieldname, datatype, sample data ... Bound Column ...
    (microsoft.public.access.forms)
  • Re: Moaning: registering Delphi 7
    ... Car keys are for the owner's protection and under owner's control and as the ... owner, you can replace the key with a red button if you so wish and while it ...
    (borland.public.delphi.non-technical)
Loading