Hi
You could do both, but I would use one schema. (the title of the mail is incorrect: many schemas is many tables, which is what I would avoid).
Regards, Thomas
--
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...@googlegroups.com.
To post to this group, send email to h2-da...@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to a topic in the Google Groups "H2 Database" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/h2-database/jp_fVH9XqXU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to h2-database...@googlegroups.com.
schema and table metadata is kept fully in memory
| From: Thomas Mueller Sent: Saturday 21 September 2013 9:50 PM To: H2 Google Group Reply To: h2-da...@googlegroups.com Subject: Re: [h2] lots of schemes vs lot of tables? |
| From: Thomas Mueller Sent: Saturday 21 September 2013 9:57 PM |