Re: detecting the existance of a table [was: undefined behaviour for sub-transactions?]

Tyler MacDonald wrote:
Tim Bunce <Tim.Bunce@xxxxxxxxx> wrote:
PostgreSQL is non-standard (and inconvenient) in this respect. 

	I chatted with Mischa (my work's resident DB guru) about this, and
according to him, the error behaviour when you attempt to SELECT from a
table that does not exist is "undetermined" in the SQL standard, so it
really is the individual DBMS' choice. I think that's actually worse; all of
these DBMs are behaving completely differently but still "correctly" on such
a basic SQL operation due to a lack of standard!


Hope you don't mind my chirping up ...

Specifying behaviour down to the detail level of executing app errors
would be enough to keep a bunch of DBMS vendors from EVER adopting
a standard. It's not like Perl. It's way more like COBOL. Hard enough to agree on what to do when the app follows the rules.

The ODBC solution was to allow any DB to express its abilities in crazy detail,
through SQLGetInfo. What kinds of joins it supported, what kinds of transaction, and then let the app do or not do what it had to ... Does DBI have something like that?

There isn't, as far as I know, except to accept the 'lowest common
denominator'. In this case that means forcing a rollback if any
statement fails.

How about having DBI implement a consistent nested-transaction interface that compliant DBMS's can support?
--
Some people think the glass is half-full.
Some people think the glass is half-empty.
Engineers think, "This glass is twice as big as it needs to be."

.

Relevant Pages

  • Re: What is the story with Server Busy
    ... If an activeX control calls your app then it will wait for ever without showing a message, but if something cross process calls your app and doesn't get a response then the message will appear. ... I put up a form for an error, and if I click on a button to debug then I return from the call to the error handler with a result code to execute the following: ... This highlights probably the BIGGEST problem in linking complex applications together via ActiveX controls, that you reach a level of complexity where you just can't tell what is causing problems. ... The original ANSI standard for C was delayed for one year - by me and two other people who were pushing hard to tighten up several things like its screwed up order of operations and arguments types in calls. ...
    (microsoft.public.vb.enterprise)
  • Access/Project/Server problem
    ... Server03 Standard Edition SP1 ... I have a process in which Access exports data to Project, opens an mpp ... App runs correctly when launched manually. ... App runs correctly when launched as scheduled task with user still ...
    (microsoft.public.windows.server.general)
  • StreamReader problem. What am I doing wrong?
    ... I'm trying to build an app that will interact with various ... console applications. ... commands to the standard input stream, and retrieve output from the standard ... standard output stream. ...
    (microsoft.public.dotnet.framework)
  • simple pro tools set-up for radio production???
    ... adopted by default as the defacto 'standard' for the most part - for ... to a simple straightforward broadcast production user interface. ... move to some computer based daw app. ... ProTools is filled with features i have no need for. ...
    (rec.audio.pro)
  • Re: Resizing form
    ... However, unless your app really needs to maximize screen space, I ... would still recommend developing at 800x600. ... Brian Schwartz ... > What is the standard resolution to create an application in so every user ...
    (microsoft.public.vb.general.discussion)