"John H. Embretsen" <[EMAIL PROTECTED]> writes: > Hmm, then why does it try to access the current schema (which may not > exist)? I haven't looked at the code, but my initial guess was that > Derby first looks for this table in the current schema. If the table is > not found there, it moves on to the schema in which the view itself is > defined.
I logged DERBY-3270 for this with a repro. Dag
