Community mailing list archives
Re: database cleanupby
Pretty much my process for testing and migrations goes (pseudocode)
Limit Value Maximum Database Size Unlimited Maximum Table Size 32 TB Maximum Row Size 1.6 TB Maximum Field Size 1 GB Maximum Rows per Table Unlimited Maximum Columns per Table 250 - 1600 depending on column types Maximum Indexes per Table Unlimited
And you can shard tables if needed although not sure Odoo supports that.
Partial and/or composite indexes that hold readily needed information based on common predicates work wonders, but even then are actually really only needed on a few really really big tables. I tested a few a while back (basically either partial on state, or active) and it made stuff all difference on a 10m row table when compared to using a sensible composite.
Well Claudal that's a nice and good approach I think. right! Thanks for the ideaOn Thu, Dec 3, 2015 at 7:37 AM, Caudal Eric <email@example.com> wrote:
I would rather have an archive/inactive field at invoice/stock moves/SO/PO level that could be setup once a year via wizard.
Then you just have to adapt the views (quite a lot though but far much cleaner in general)Well MartinDepending in which country you are living data has to be kept for a certain time - in Thailand it is 5 years - and afterwards you should actually try to get rid of it as also here they call it privacy etc (even no one seems to check it as long as your neighbour does not tell them!)A growing database also results in speed and performance losses. Especially if you have lots of other stuff stored there to. i.e. from the website module and you want to get rid of old articles or stuff which is not at all relevant for seo anymore.Removing transactions within a year can be dangerous, you are absolutely right! I would not advise it either. But anyway an easy way to cut of all data no more needed would be fine.Otherwise you are ending u like a Facebook Backup which is 2-3 or even more GB to be downloaded, even you would need only the last months or only a certain part of it, what has been stored in the DB.On Wed, Dec 2, 2015 at 10:32 PM, Martin Trigaux <firstname.lastname@example.org> wrote:On 02/12/15 16:12, Andreas Becker wrote: > This is a very good question - Keeping your database clean should be > easy as it would be good to do this every year at least. I don't really think that's a good idea. Removing some records such as accounting transactions or other moves is a risk to lose information, break flows or be stuck at migrations. I wouldn't advise it if you don't know exactly what you are doing or have very good reason to do so (other than "keep my db tidy"). @Franco you ask something very specific (remove this but keep that) so this should probably be a manual operation. But again I wouldn't advise it. And, as said Pedro, make copy of your database. -- Martin Trigaux Odoo (Formerly OpenERP) https://odoo.com https://github.com/mart-e
Eric Caudal (from my mobile)