Afternoon all,

In the past, I've seen some scripts that did some DDL commands then a
COMMIT afterwards. I think it was for running under IBObjects, but don't
quote me.

I'm QA'ing a script for an app we have here which is creating a pile of
tables and indices etc, and has no COMMIT after any of these.

The Firebird Book mentions on page 784 that isql will start a special
transaction for DDL and commit immediately afterwards. This is fine and
I'm happy with that.

What does embedded Firebird do in this situation? I'm of the opinion
that we should only use E-FB when the database has been designed and
built (and populated?) and the application does the usual CrUD stuff.
However, this script I', QA'ing is for a patch which needs to update the
database structure and I'm curious as to whether or not I need to get
them to COMMIT afterwards or not.

The database is embedded Firebird 2.1.x running on 32 bit Windows 2000.
The application is, unfortunately, Java based and *may* do the commit's
itself internally, but there are none in the script.

So that's the background, should I ask the vendor to add a COMMIT at
strategic places in the patch script or am I ok as the reference to isql
in the book implies all DDL executed against the database regardless of
the tool used to connect and execute said statements?


Many thanks.


Cheers,
Norman.

Norman Dunbar
Dunbar IT Consultants Ltd
Orchard House
10a Greenacre Park Mews
Rawdon
Leeds
LS19 6RT

Tel: 0779 3292 984
Tel: 0773 4531 439


Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk

Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.

If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk