Hi, I am considering using linked tables but I am not sure how they work. Could someone please describe how H2 does its magic for linked tables and if there are any glaring problems with using them for my situation?
I have a large database (greenplum: based on postgres) where I create a single sparse table (read-only). My naive approach is to pull the entire table into a H2 in memory database so I can access it in the fastest possible way: resultset = select * from greenplum_table for each resultset_row insert resultset_row into h2_table The table is read only in H2 as well. However I do need to handle the case when the H2 server is shutdown for maintenance. I plan to use the backup and restore scripts to dump the in memory tables to disk during shutdown and load them during startup. This will remove the need to pull all the data from greenplum again. >From my very limited knowledge it would seem that linked tables may be a more effective solution: link h2_table to greenplum_table access h2_table When the server needs to shutdown all I need to do is keep track of the tables I have linked and then re-link during startup. Any information/advice is appreciated. Thanks, Ty --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
