Re: What is a long transaction
Hi Stephane,
I do this all the time. I use dbload which allows to specify how many rows
to load before doing a commit. I suggest taking a look at that utility. A
long transaction occurs when you ask the system to log a great of
information in one transaction. The engine logs the transactions pending
insertion and actually does the insertions when it receives a commit
command. If it receives a rollback command it removes the transactions
from the log and doesn't update the database. This is simplified and I am
sure someone will point that out, but it is the essence of what happens. A
transaction is what you ask the engine to do between the time you send a
begin work command a commit or rollback work command. If there is more in
between those two command than can be logged, it says, the transaction is
too long and rolls it back. :)
----------
} From: Stephane Magnan <stephane.magnan@eur.autodesk.com>
} To: informix-list@rmy.emory.edu
} Subject: What is a long transaction
} Date: Thursday, March 13, 1997 07:20
}
} Hello,
}
} If I load a file with sql statement 'load from filename' and
} in this file there are 116'000 rows (insert).
}
} Do I get a long transaction ?
}
} Do commit or rollback terminate a transaction ?
}
}
} Do we see one or 3 transactions above ?
}
} insert into table values (...)
} insert into table values (...)
} insert into table values (...)
}
} I have some problem to understand what is a transaction.
} As I must load the file with 116'000 rows (insert) I'm afraid to
have
} a long transaction and that the process abort.
}
} Thanks in advance for your help.
}
} Stephane