On 7/13/07, Ed W <[EMAIL PROTECTED]> wrote:
> Well I think you just highlighted that different sorts of locks are
> suitable for different areas of the app!
Agreed.
> I would agree that batch jobs need pessamistic locking though - or more
> precisely it's no good getting to the end of your 20 min
Victor Sterpu wrote:
> I'm want to make a inventory function that to print the inventory at a
> specific date.
> The inventory must show the quantities and also the value of the
> inventory account for each group of products.
> So it will show the quantities and the values of the ramaining items.
Well I think you just highlighted that different sorts of locks are
suitable for different areas of the app! More granular locking is
always nice, but I guess you just need to do whatever is most sensible
given the structure of the app!
I would agree that batch jobs need pessamistic locking th
Chris Travers wrote:
On 7/13/07, Victor Sterpu <[EMAIL PROTECTED]> wrote:
I'm want to make a inventory function that to print the inventory at a
specific date.
The inventory must show the quantities and also the value of the
inventory account for each group of products.
So it will show the qu
On 7/13/07, Victor Sterpu <[EMAIL PROTECTED]> wrote:
> I'm want to make a inventory function that to print the inventory at a
> specific date.
> The inventory must show the quantities and also the value of the
> inventory account for each group of products.
> So it will show the quantities and the
I'm want to make a inventory function that to print the inventory at a
specific date.
The inventory must show the quantities and also the value of the
inventory account for each group of products.
So it will show the quantities and the values of the ramaining items.
Do you want to integrate sutc
On 7/13/07, Barry Michels <[EMAIL PROTECTED]> wrote:
> We have 3 offices in our company and currently use 3 copies of
> QuickBooks. What is the best way to use LedgerSMB in our situation? We
> would like to be able to use the same master inventory list so updates
> only have to happen once for al
We have 3 offices in our company and currently use 3 copies of
QuickBooks. What is the best way to use LedgerSMB in our situation? We
would like to be able to use the same master inventory list so updates
only have to happen once for all 3 locations. But, we would like each
of the 3 location
On 7/13/07, Ed W <[EMAIL PROTECTED]> wrote:
>
> > Any session based system I've used has the issue of stale sessions,
> > multiple sessions and browsers discovering 'old' sessions and using
> > them.
> >
>
> I think it should be much less prevelant than that if the system is
> implemented well.
>
>
> Actually, I would think a row-level trigger would be more appropriate.
>
Not possible in 1.3 unless we also decide to just scrap that release
and go straight to 2.0.
The reason is, a single check hits a surprising number of rows in one
table in the codebase we have inherited. I expect this to c
On Fri, Jul 13, 2007 at 01:05:01PM +0100, Ed W wrote:
> Also "locking" is usually a pain. Much better to go for "optimistic
> locking" which means that two uses are allowed to have a go at updating
> or printing something, but one of them wins and the other gets returned
> an error. There are
> Any session based system I've used has the issue of stale sessions,
> multiple sessions and browsers discovering 'old' sessions and using
> them.
>
I think it should be much less prevelant than that if the system is
implemented well.
> The issue of timing out sessions is a tough one. Ther
> The use of session tables sounds like unnecessary overhead.
>
> Ciao,
>
> David A. Bandel
Hiya all,
I really like the idea of triggers. It sounds like it would involve a
lot less coding - which is nearly always a good thing. Plus it would
give a tighter integration to the logic in the db idea
On 7/13/07, Chris Travers <[EMAIL PROTECTED]> wrote:
> Hi all;
>
> One of the problems that can occur in concurrent use, especially with
> payment processing is that two users could indeed run the same
> payments, print duplicate checks, etc. This is a risk relating to
> paying vendors, and could
14 matches
Mail list logo
