Hi, Please use another subject, don't just reply to the "New version available" subject.
> (1) It's planned a "SELECT INTO new_table" or "CREATE TABLE as > ( select_resultset )" or materialized views aka DB2 ? CREATE TABLE AS SELECT is already supported. Materialized views are not supported, those are tricky to implement. > (2) If I have many LINKED TABLES defined to the same database, with > the same driver and with the same user , > same connection settings (isolation level, autocommit, etc.), > can I be sure that only one connection will be done for all this > linked tables ? > Can this mono/multi connection behavior controlled in some way ? Yes, this is already supported. See the changelogs of version 1.0.79 (2008-09-26) > can I be sure that only one copy of JDBC driver will be loaded ? I'm not sure if this question is related to LINKED TABLES. > (3) From (2) , When and How long will be connected the other > datasource ? > It's connected at startup or lazy until this linked table is used in > some query ? > Can this behavior be controlled in some way ? When the database is opened, but if the linked database is not accessible at that time then later when accessing the table. Why is that important for you? Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
