> I'm gona use h2 in my product. but database size is huge.
> So table partitioning is very important!!! (for my product)
> I hope that this feature will be implemented.
I will add a feature request, but so far this feature does have low
priority for me (I'm sorry). That will change if other people also
request it of course. There are a few workarounds: one is to partition
tables 'manually' in the application, and use linked tables so that
each table partition is stored in a different database.
Regards,
Thomas
Hi Thomas,
increment your counter by one (me).
I have some apps that can't port to H2 because lack of partitioning.
Tipical case are simple models with few dependent tables and one or few
_very_ large tables.
Use cases like reporting from automation captured data, PBX data or
telco like accounting where you have a good natural partitioning key
(ex. account no.)
and the same key drive almost any data navigation case.
For this type of applications partitioning really help.
Regards,
Dario.
> Thank you for your suggestion.
> but I think this function is not table partitioning function.
As far as I understand, don't have enough space on one device, right?
Or is it a different problem? If the problem is just space, then I
guess splitting the file should solve it.
> I want to use table partitioning. (like Composite Range-List
> Partitioning)
Why?
> ( the partition can backup/recover/drop/add/... )
With the split feature, you could do that as well as far as I understand.
Regards,
Thomas