Re: TDBC documentation, examples, syntax?

On Feb 19, 1:15 pm, George Peter Staplin <georg...@xxxxxxxxxxxx>
wrote:
tom.rmadilo wrote:
On Feb 10, 6:57 am, suchenwi <richard.suchenwirth-
bauersa...@xxxxxxxxxxx> wrote:
On 9 Feb., 21:59, "stoli...@xxxxxxxxx" <stoli...@xxxxxxxxx> wrote:

I see that TDBC is being included in 8.6. I have downloaded and have
started to experiment however I cannot seem to find any useful
documentation or examples to start from. The TIP 308 doesn't really
cover syntax and tcl.tk/docs doesn't seem to cover it either. I've
hunted the wiki, sourceforge and google.

Has a syntax document been created? A complete example script
available?

Some examples are athttp://wiki.tcl.tk/20343-internally, you'd have
to use SQL anyway, for which there are various docus.

Wow! The TDBC is amazingly bad. When I say bad, I mean really, really,
really bad. Everyone who knows what day it is knows that ODBC is the
base standard. If you want generic, start with ODBC.

Tom, with all due lack of respect, why don't you list the flaws instead of
using vague, unclear, and emotional reasoning?

What we have is TIP 308. What a disaster! This is what you should
expect when a programmer designs a database interface. Get a clue!
There is no "abstraction" in your API.

So you're insulting programmers, and using emotional reasoning.  What do you
do for a living?

I'm not sure what you mean by "emotional reasoning"? The contents of
TIP 308 is irrational and unrelated to current database interface
standards. Please read at least the CLI portion of the most recent SQL
standard. That is ISO/IEC 9075.

Maybe you think I am dissing programmers. No! I'm dissing programmers
who are trying to reinvent thousands of hours of work by other
programmers to develop a standard interface. We have an existing
interface definition, somewhat beyond ODBC. When you throw this out
the window you must provide not only your own interface, but a mapping
of your interface to the standard.

Hopefully everyone recognizes that in the end the Tcl client must
communicate with an actual database server. If the Tcl API fails to
reflect the standard database API, huge translation problems should be
expected.

This is not emotional reasoning, this is practical outrage over an
untethered API. Anyway, if you wish to develop a database API and you
have not read ISO/IEC 9075, you are a clueless idiot. Why would you
develop a generic SQL API which ignores the industry standard generic
SQL API? A rational person would not. A rational person would be
outraged when some idiot attempted to weave their own perfect solution
into an already solved problem.
.

Relevant Pages

  • Re: TDBC documentation, examples, syntax?
    ... This standard is long, ... code, but ISO 9075 contains more than an interface, it defines an SQL ... What I see in the TDBC API is a distinct, ... layer API", this is what we see as we write Tcl programs. ...
    (comp.lang.tcl)
  • Re: API troulble
    ... talks to the database, but offers an API to allow other programmers in any ... interface, so that I can group functionality neatly - one to handle file ... it would work as Excel - the application instantiates other objects and ...
    (microsoft.public.vc.mfc)
  • Re: My Enterprise Architecture - your thoughts?
    ... > maps the data to the relational database using the data layer. ... In the enterprise environments in which I work, reporting is a huge ... of the many standard SQL based report writers. ... relational data interface as just another data interface. ...
    (comp.object)
  • Re: C API??
    ... >I assume API means Application Programming Interface, that is, the standard ... Note the word "interface". ... an API makes the term pointless. ...
    (comp.lang.c)
  • Re: SQL using C
    ... I am almost a new C programmer and now I need to use SQL within my C ... The people who are telling you to use a C API are out of their mind. ... an ODBC or SQL/CLI interface ... If you use a proprietary database API, ...
    (comp.lang.c)