Meaning of "Bad Request"?

Meaning of "Bad Request"?

Post by Stephen Moh » Sat, 29 Jun 2002 02:39:30

I have an updategram which uses a mapping schema.  It works as a template or
when POSTed from HTML (per the SDK example).  I try to post it from BizTalk
Server  and receive the following error:

Error code:80004005
====== ERROR =====

The HTTP server returned an unexpected response: 400 100 Bad Request

The mapping schema is in the schema subdir, the mapping-schema attribute
does not use a URL, e.g., mapping-schema="hr_map.xsd", as POSTs don't permit
this.  Security issues have been resolved.  Does anyone know the meaning of
the above error?  Is it indicative of an inability to get hold of the
mapping schema?  Do I have the mapping schema in the right place?


1. "Transactions are bad, real bad" - discuss

In an article under the thread "Do Data Models Need to [be] built on a
Mathematical Concept?", Paul Vernon commented:
 > Dead wrong. Transactions are bad, real bad. In short they are not
 > compatible with the 'arrow of time'. They let you freeze time and
 > that is not a good model of reality. Start a new thread if you want
 >  to discuss the details, I've a draft paper on the subject and a
 > could do with some intelligent challenges to sharpen up my
 > argument.

Herewith, a new thread - unless someone else got there first.

I'm sympathetic to the Date/Darwen view (espoused in The Third
Manifesto and in Temporal Data) that a single statement should be the
scope of a transaction, once you allow what would currently be a
sequence of statements to be treated as a unit -- using the SQL notation:

UPDATE Table1 SET ... ,
UPDATE Table2 SET ... ,
INSERT INTO Table3 ... ,
DELETE FROM Table4 ...;

All four operations are part of a single compound statement and
collectively form a single transaction.

Is that anything remotely resembling what you're thinking, Paul?

I assume that you're not arguing that it is unnecessary to have
something akin to a transaction, (or a saga, or a set of compensating
actions), in the sequence:

UPDATE Accounts
     SET Balance = Balance - 1000000
     WHERE AcountOwner = 'Paul Vernon';
UPDATE Accounts
     SET Balance = Balance + 1000000
     WHERE AccountOwner = 'Jonathan Leffler';

If the two UPDATE operations are not treated somewhat atomically - if
the first can succeed and yet the second can fail (boo, hoo) without
somehow undoing the first - then Paul is 1000000 currency units (GBP)
out of pocket (and so am I, but I didn't have them in the first place,
whereas maybe Paul did, and more significantly, maybe he now owes the
bank those currency units he didn't already have in his posession).

Jonathan Leffler                   #include <disclaimer.h>

Guardian of DBD::Informix v2003.04 --

2. Help files in P5

3. max of ("...","...","..")

4. Distinct - OrderBy - what is it?

5. Meaning of "Reads" column in Profiler

6. pgsql/. configure

7. Meaning of "GO" in Transact SQL

8. BDE lock-error information on Borland BDE-support TI-pages.

9. meaning of "declarative"

10. Meaning of message "First Chance Exception"

11. Meaning of "number of worker processes"

12. What does it mean "Fuzzy Checkpoint"?

13. meaning of "unexpected error: link range"