Re: calc: jumbo sheets on windows (never gonna happen)

Dan Lewis <elderdanlewis@xxxxxxxxx> · Tue, 6 Oct 2020 21:50:37 -0400



    I would use MySQL as a back end. In a database, all the
      calculations that you mention are created in queries using SQL.
      And yes, MySQL can handle tables with millions of rows of data.
      But there is a lot of learning that has to be done to learn how to
      use MySQL. Setting up the tables takes some time and understanding
      as well. 

    
    Dan

    
    On 10/6/20 17:10, nicholas ferguson
      wrote:

    
        Can I ask what kind of
              platform would you use for 16 million rows that involve
              calculations?
         
        
            From: LibreOffice
                  [mailto:libreoffice-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Dan
                  Lewis

                  Sent:
                  Tuesday, October 06, 2020 2:59 PM

                  To:
                  libreoffice@xxxxxxxxxxxxxxxxxxxxx

                  Subject:
                  Re: calc: jumbo sheets on windows (never gonna happen)
          
        
        From my perspective, one needs to
              learn how to create a database in Base including tables,
              queries, forms and report when working with this much
              data. It is designed to handle large amounts of it. MySQL,
              Postgresql, and Oracle can be used as a backend  for Base
              being the front end.
        Dan
        
          On 10/6/20 12:09, Noel Grandin wrote:
        
        
              Hi
            
            
              i.e. very large spreadsheets of up
                    to 16 million rows.
            
            
              So I did some more investigation
                    into this. In various places, we need to accumulate
                    things like row-heights and other things, numbers
                    which, with jumbo sheets, easily exceed 32-bits.
            
            
              HOWEVER
            
            
              All over the place, we pass these
                    values through sal_uLong/sal_Long/long/unsigned
                    long.
            
            
              Which is 32-bits on Windows. Doh!
            
            
              Honestly, the only solution I can
                    think of (and one I confidently expect us to
                    reject), is that we declare a flag day, and search
                    and replace sal_Long/sal_uLong/long/unsigned long
                    with a 64-bit type across the ENTIRE code base.
            
            
              Regards, Noel Grandin.
            
            
          _______________________________________________
          LibreOffice mailing list
          LibreOffice@xxxxxxxxxxxxxxxxxxxxx
          https://lists.freedesktop.org/mailman/listinfo/libreoffice
        
      
_______________________________________________
LibreOffice mailing list
LibreOffice@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/libreoffice