There seems to be a flaw in the meta schema's cross_references view.
Here's how to reproduce:

-----------------------------------
create table a(id int primary key);
create table b(a_ref int, foreign key (a_ref) references a(id));

-- This displays a generated constraint name for the primary key
select constraint_name from information_schema.constraints where
table_name = 'A';

-- This displays a generated foreign key name, but no primary key name
select fk_name, pk_name from information_schema.cross_references where
pktable_name = 'A';
-----------------------------------

I am using version 1.3.153. I didn't make regression checks.

-- 
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.

Reply via email to