Note that there are some explanatory texts on larger screens.

plurals
  1. USKim Sullivan
    primarykey
    data
    text
    plurals
    1. COI think you misunderstand, I don't need a weekly aggregate after the week has ended, I need it during the week (as a part of stock keeping). That means that when I'm processing a sale for product 123456 for customer 100000, on Wednesday 13:45, I need the total sales for the article from monday 00:00 until the start of the transaction on Wednesday. If every time I want to sell a product to a customer I have to do a 'SELECT .. GROUP BY' on the sales data, the database just won't be able to keep up. This is why I have to do an incremental update of the aggregate after each sale.
      singulars
    2. COHm, I probably could rebase the changes on the development branch ("dirty") once in a while (actually, before merging to stable and releasing), so I don't have all those intermediate binaries I don't care about much. The only important thing between stable releases is the hash and the commit messages... The hash is important for testing (which build was tested and which was not). I'll have to think about it some more.
      singulars
    3. COI hope the question makes more sense now. The problem is with repository size and slow connections. I was hoping there was a way to use a single git repository for deployment for both testing and stable binaries. But the more I think about this, the more I come to realize that Git just wasn't designed to do this. I'll either have to accept the high bandwidth cost associated with pulling both deployment and stable binaries, or use some other mechanism (maybe a centralised versioning system, or lots of shell scripts that "version" the binaries on a plain filesystem and deploy using plain copy).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload