RE: RPG Native IO with SQL unique constraint

I agree this sounds more like a design problem than anything else in
this particular case. Orders are sometimes constrained to a single
instance of a product but if multiple lines with the same product are
allowed, there are not usually any other restrictions. The customer
wants 10 now and 10 with a delayed delivery date. A line with 10 units
is added to a backorder that also ships 10 units. I would not want to
explain to the Sales Dept. that customer must choose different
quantities.

The Native I/O problem of updating a set of records instead of as
individual record updates requires commitment control. The problem you
describe should be solved by using embedded SQL and committing the
updates. RPG does have native I/O COMMIT...not sure if it would address
your problem.


-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Tuesday, September 08, 2009 09:56
To: RPG programming on the IBM i / System i
Subject: Re: RPG Native IO with SQL unique constraint

I'm with Simon.

The constraint as described makes no sense.

In 20+ years, I don't recall ever coming across a unique constraint
that involved a quantity field.

Charles