Yes, I see the point. PageBtreeIndex is a bit to deep and to specific. Studying the code to more detail, I've found RegularTable to do 90% of what I need. It must get a custom ScanIndex and a way to update all indexes but the ScanIndex (for changes coming from the Notes side). And that's it. Of course I must write a ScanIndex that links to the Notes Database (but that's the more familiar part ;-) ) I'll give that a try and let you know of the outcomings ... ;-)
Thanks a lot for any help and hints! Am Donnerstag, 29. Oktober 2015 08:27:20 UTC+1 schrieb Noel Grandin: > > > You want to start by subclassing TableEngine for your custom table. > From there I would just create regular MVStore tables to hold your > indexes. > Since the MVStore provides a java.util.Map type API, that would be a > natural way of storing your indexes. > > If you really need the stability of using the older PageStore engine, then > it gets trickier, and you'll probably need to > cut and paste the PageBtreeIndex class and modify it for your use-case. > > > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
