none
DB structure for a POS application. RRS feed

  • Question

  • Hi!

    I need to implement a PointOfSale solution. I would like to ask the advice of those more experienced than me in the following issues:
    1. Which is more optimal: to keep the goods entries in one table and the exits in another or to keep them in the same table with an identification field?
    2. What is the best (quick) way to calculate the current stock for an item? Do I have to add all the entries from which I subtract a sum of all the outputs for that article? If the volume of operations is large, the operation will be time consuming ... I was thinking of creating an additional table in which to save the stock at the end of each month, and the calculation to do it only for the current month, but this makes it difficult to operate documents before the end of the month ...

    Is there a good practice manual somewhere in designing the database for this type of application?

    Thank you!

    Monday, July 6, 2020 7:11 PM

All replies