Hi,
it's hard to say without seeing more code. In my mind right now is
something like:
* First transaction start
** T1: It reads maximum from DB (lets say is 100)
** T1: It will create 101
** T1: It will create 102
* T2: Let say at this moment second transaction start
** T2: It reads maximum from D
Hello! Thank you for answering. So if that's the case then what is
happening is that (according to question 1) the second transaction is
getting the same number as the first one and complaining with the
IntegrityError while trying to save. Is that correct?
On Wednesday, October 21, 2015 at 10:
Hi,
Transactions are a different concept than locks. In few words a transaction
means that the all the sentences within it are done or not done, but can't
be half done (unless you have savepoints, and want to rollback to a
particular point). The locks avoid other for making operations on the table
Anyone? T_T
On Tuesday, October 20, 2015 at 1:02:27 PM UTC-5, César Bustíos Benites
wrote:
>
> Hello, first, let me give you an idea of the problem I'm facing. This is a
> company with a fruit packaging plant, they use several printers for the
> barcodes they attach in fruit boxes, clamshells a
Hello, first, let me give you an idea of the problem I'm facing. This is a
company with a fruit packaging plant, they use several printers for the
barcodes they attach in fruit boxes, clamshells and pallets. There is a
Django table that keeps track of the current number for each one (caja,
clam
5 matches
Mail list logo
