RE: Stupid question
Thomas J. Girsch wrote:
...snip...
}
} If (for example) the INSERT statement fails, the script does not abort; =
it
} keeps right on going. So the "begin work" succeeds, the "insert" fails, =
the
} "delete" succeeds, and the "commit work" succeeds. Your "history dump" =
has
} just deleted the current records WITHOUT first successfully inserting =
into
} history. In other words, scripts like this don't stop on an error. =
They
} happily keep right on going.
}
} There is a way to work around this: set DBACCESSNOIGN to a nonzero =
value,
} as in:
}
} DBACCESSNOIGN=3D1
} export DBACCESSNOIGN
}
} Hope this helps,
}
} - Thomas J. Girsch
} Database Systems Manager
} Arch Communications Group, Inc.
} "Mr. Himnesh Kapoor" wrote in message =
<67ac96$5o7@cssun.mathcs.emory.edu>...
} >Write your script like this.
} >
} >dbaccess <database name> <<!
} >sql statement
} >!
} >
}
Thomas:
I was very interested in the existence of this environment variable, and =
tried it out. It does not work on either our DEC Alpha or our SNI machine =
(where I want it, because I don't have isql). Our very helpful local =
support (Australia) had a look around their on-line documentation, and it =
turns out that this variable is actually DBACCNOIGN (at least in version =
7).
HTH
RET
+------------------------------------------+
| Richard Thomas |
| DBA - Marketing Information Systems |
| Optus Communications |
| email: richard_thomas@yes.optus.com.au |
| Ph: +61 2 9342 7188 |
| "My opinions are my opinions" |
+------------------------------------------+