title: "Column not found" when selecting from a table in a different schema
body: <p>I'm experiencing a very weird issue with H2.</p>
  
  <p>In addition to all the tables residing in default ("PUBLIC") schema, I have several tables created in a separate schema (there's a valid business reason to do it that way, but it's irrelevant here). When I run</p>
  
  <pre><code>select * from schema1.table1
  </code></pre>
  
  <p>everything works perfectly. If I try to do the same but mention the column name(s) explicitly, e.g.</p>
  
  <pre><code>select col1, col2 from schema1.table1
  </code></pre>
  
  <p>the query fails with "Column col1 not found; 42S22/42122" error. This occurs whenever the column is referenced anywhere in select (from clause / where clause / etc...).</p>
  
  <p>Column names are correct and they show up in <code>INFORMATION_SCHEMA</code>. Furthermore, if I quote them, query works properly - however this has a side effect of making column names case sensitive which then fails in Hibernate which apparently uppercases them anyway.</p>
  
  <p>Am I overlooking something obvious here? Is there a reason for this bizarre behavior or is this a bug?</p>
  
  <p><strong>Update</strong>: Thomas's answer made me realize that the issue was not with a different schema but rather with how tables in that schema were created; specifically the use of quoted identifiers. Here's a script that reproduces the problem in H2 1.3.161 (latest version atm):</p>
  
  <pre><code>create table table1(col1 int, "col2" int);
  insert into table1 values(1, 1);
  select * from table1; -- works
  select col1 from table1; -- works
  select "col2" from table1; -- works
  select col2 from table1; -- fails
  </code></pre>
  
  <p>I don't understand why there's a difference between the last 2 queries. Column name is case-sensitive here (because it was defined via quoted identifier), but it does have the correct case. <code>INFORMATION_SCHEMA</code>.<code>COLUMNS</code> shows no differences (aside from name) between the two columns either. Is case insensivity for unquoted columns obtained by forcibly uppercasing all queries?</p>
  
  <p>The above script works as expected (as in all queries complete successfully) in Postgres.</p>