I need an advice for a database problem related to the v18 4D View Pro.
As said in another post (https://forums.4d.com/Post/IT/29978300/1/29978301#29978301) my company massively relies on 4D View sheets.
One of our simplest sheets may be like this
33939583;“Example of a sheet”[/]
With text, borders, formulas, different backgrounds, different fonts, about 30 columns and 100 rows. Other sheets may have also images.
This 4D View document, exported as 4PV has a size of 27kB.
This 4D View document, stored in a compressed blob has a size of 3kB.
If I convert this sheet from View to View Pro the stringified JSON has a size of 243kB. Because there are a lot of redundant attributes for these 30x100 cells.
The 4VP file has the same size of 243kB.
If I put the object in a blob, the resulting blob has a size of 433 kB.
If I put the object in a blob and I compress it, the resulting blob has a size of 10 kB.
The excel converted file has a size of 16kB.
33939591;“Your comment here…”[/]
Currently we store in our main v17 database about 700 000 compressed blobs containing a 4D View sheet.
I really loved the idea to use objects with all their features, but in these conditions it’s not sustainable.
Do I really have to store all the 4D View Pro objects in compressed blobs (tripling anyway the space needed in comparison to the old 4D View)? Do you have other ideas?
Thanks to whoever contributes