BEGIN WORK

BEGIN WORK

Post by Irina Kotlov » Sun, 31 Dec 1899 09:00:00



This is a multi-part message in MIME format.

------=_NextPart_000_0254_01BDD7F6.17449860
Content-Type: text/plain;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

Hello!

Absolutely stupid question.
If DB is started without transaction log, then will the statements BEGIN =
WORK - COMMIT WORK have any effect on DB? I expect that NO.

Thank you in advance,
Irina

Irina Kotlova
RESEARCH & TRADE RUSSIA

phone: +7 095 959-43-13 (additional 24)

------=_NextPart_000_0254_01BDD7F6.17449860
Content-Type: text/html;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3D"text/html; charset=3Dwindows-1251" =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#d1f1f8>
<DIV><FONT color=3D#000000>Hello!</FONT></DIV>
<DIV><FONT color=3D#000000></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000>Absolutely stupid question.</FONT></DIV>
<DIV><FONT color=3D#000000></FONT>If DB is started without transaction =
log, then=20
will the statements BEGIN WORK - COMMIT WORK have any effect on DB? I =
expect=20
that NO.&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thank you in advance,</DIV>
<DIV>Irina</DIV>
<DIV><FONT color=3D#000000><BR>Irina Kotlova<BR>RESEARCH &amp; TRADE=20

<A=20

+7 095=20
959-43-13 (additional 24)<BR></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0254_01BDD7F6.17449860--

 
 
 

BEGIN WORK

Post by Scott Kolay » Sun, 31 Dec 1899 09:00:00


The engine will return a sql error -256 "transaction not available" to the
calling program.

Scott Kolaya

>Hello!

>Absolutely stupid question.
>If DB is started without transaction log, then will the statements BEGIN =
>WORK - COMMIT WORK have any effect on DB? I expect that NO.

>Thank you in advance,
>Irina

>Irina Kotlova
>RESEARCH & TRADE RUSSIA

>phone: +7 095 959-43-13 (additional 24)


 
 
 

BEGIN WORK

Post by Robert Stuar » Sun, 31 Dec 1899 09:00:00


The DB will be OK, but your program won't!

If you don't trap the situation, a 4gl will just fall over,
    sql scripts will stop at this point.

Cheers

Robert Stuart


> This is a multi-part message in MIME format.

> ------=_NextPart_000_0254_01BDD7F6.17449860
> Content-Type: text/plain;
>         charset="windows-1251"
> Content-Transfer-Encoding: quoted-printable

> Hello!

> Absolutely stupid question.
> If DB is started without transaction log, then will the statements BEGIN =
> WORK - COMMIT WORK have any effect on DB? I expect that NO.

> Thank you in advance,
> Irina

> Irina Kotlova
> RESEARCH & TRADE RUSSIA

> phone: +7 095 959-43-13 (additional 24)

 
 
 

1. BEGIN WORK/COMIT WORK in stored procedure

Can a transaction be defined in a stored procedure.

Something like -

CREATE PROCEDURE a()

FOR EACH

  BEGIN WORK
  INSERT......
  <more stuff>
  COMMIT WORK

END FOREACH;

END PROCEDURE;

Thanks for any help...

Frank  

2. Field sizes and structure

3. ISQL Begin Work & Commit Work

4. Bug in 7.3.3 for Solaris

5. begin works and commit works in

6. Identifying a stored procedure "version"

7. begin works and commit works in storeprocs

8. Msg 15009, Level 16, State 1

9. ISQL Begin Work & Commit Work

10. Implicit Begin Work???

11. Perl DBD::Informix BEGIN WORK WITHOUT REPLICATION

12. Begin work