Subject Re: [firebird-support] Design problem
Author Tim Ledgerwood
The shift close procedure can take several minutes (between 30 s and 4
minutes) to complete. During this time, if I am trying to insert a new
sale, I get a no wait lock conflict.

At 12:40 PM 06/20/2003 +0200, you wrote:

>Hi Tim,
>
> > Need some advice. I have a log table in my database, that records every
> > transaction passed to it from fuel pumps and points of sale at Petrol
>Stations.
> >
> > So far so good - no problem there.
> >
> > About once every 8 hours, the shift at the petrol station changes, and the
> > system goes through a "change shift" procedure. During this procedure,
> > various reports on income, expenditure, stock and fuel levels are drawn,
> > based heavily on the data in the LOG table.
> >
> > This is where the problem comes in. I cannot afford any lock conflicts AT
> > ALL - i.e., the fuel pumps cannot stop pumping to accommodate a shift
>change.
>
>What lock conflicts?
>
>
>With regards,
>
>Martijn Tonies
>Database Workbench - the developer tool for InterBase & Firebird
>Upscene Productions
>http://www.upscene.com
>
>
>
>To unsubscribe from this group, send an email to:
>firebird-support-unsubscribe@yahoogroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.489 / Virus Database: 288 - Release Date: 06/10/2003


[Non-text portions of this message have been removed]