[Please don't top post as it makes the discussion more difficult to
follow.]
On Aug 7, 2007, at 9:05 , Kenji Morishige wrote:
On Tue, Aug 07, 2007 at 12:23:00PM +0200, Nis Jørgensen wrote:
This doesn't solve your problem, but might simplify the query to
find a
new id - something like th
Actually, I already have a resource table that stores the uid of the item in
question. The checkout table does double duty as a history mechanism and a
check-out mechanism. I think you are on the right track, I should seperate
these two tasks and possibly create another table. The actual design
Kenji Morishige skrev:
> I have a table that creates "check-out" records that stores information when
> a particular resource is being utilized. I want to maintain a friendly
> shortened ID so people can reference these check outs.
>
> At any given time, there should not be more than 99 or so
I have a table that creates "check-out" records that stores information when
a particular resource is being utilized. I want to maintain a friendly
shortened ID so people can reference these check outs.
At any given time, there should not be more than 99 or so check-outs, so
as the check-outs
