Issue 6763 - "easy" 32000 row limitation workaround
Summary: "easy" 32000 row limitation workaround
Status: CLOSED WONT_FIX
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: ooo
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-05 18:30 UTC by lars
Modified: 2003-09-08 16:55 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description lars 2002-08-05 18:30:45 UTC
How about:

when one row or column limit is reached, the last row or column is marked 
as "continued in ..." and the rows or columns of the next sheet are used.

When sheets are used up, a new Calc document is created where the sheets 
continue.

This can be done "behind the back" ie it's not visible to the user but only 
internally and the user is presented with infinte rows, columns and sheets - 
displaying should be no problem, but "data processing" is executed on new 
sheets or documents as said.


Implementing this "workaround" should be more easy and fast and therefore be a 
good way in the meantime while you work on "really" removing the limitation.


And when you reimplement the "table" model - you should go the way of infinite 
rows etc.


Lars
Comment 1 ooo 2002-08-05 20:36:44 UTC
Don't know what gave you the impression but implementing this
workaround wouldn't be in no way easier than working on the row-limit
plan already lined out.
Comment 2 ooo 2002-08-05 20:37:25 UTC
closing
Comment 3 peter.junge 2002-08-06 09:18:59 UTC
And, we consired to stop working around. If somethings done it should
be done neat.
Regards, Peter

+1 closed
Comment 4 lars 2002-08-06 16:09:52 UTC
just an explanation:

i thought of it working like "verkettete listen" (data management) 
where one can wrap those containers by an overloaded C++ operator [], 
so access is the same as an array even though the underlying storage 
is "spread".

Now as a user can manually use x*32000 rows by using several sheets, 
this can as well be "executed" automatically by the software.

Of course it needs some code written but it should be "doable" within 
2 days especially if one knows the spreadsheet table sourcecode.


And "If somethings done it should be done neat" :  I  aggree!

But as a intermediate solution... it's good (actually really) and one 
doesn't have to wait 5+ months.